startupitem: add new option startupitem.logfile.stderr, for capturing stderr #296
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Presently, when
startupitem.logfile
is specified, we add a plist entry for stdout logging (viaStandardOutPath
). But when errors and such occur - particularly due to a fatal startup issue - that output often goes to stderr.Not capturing the latter, makes troubleshooting more difficult for users. Potentially requiring them to manually edit the plist file, to add an entry for
StandardErrorPath
themselves.To ensure the user doesn't have to deal with that, add new option
startupitem.logfile.stderr
.By default, it is set to
startupitem.logfile
. But the user can specify a different logfile, clear the value (to disable stderr logging), or set it independently ofstartupitem.logfile
(if only stderr should be logged).Fixes: https://trac.macports.org/ticket/67955