Correct log_file's inconsistent behavior #9700
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pralkarz
changed the title
pralkarz
changed the title
pralkarz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Close #7336
Per @symonk's comment on that issue I took his PR #7350 as a starting point, and extended it per @bluetech's first insight in that PR. Not sure whether I should tackle the second one as well,
In summary:
--log-fileis passed as a cli argument, its location is relative to the invocation path.--log-fileisn't passed as a cli argument andlog_fileoption is present in the config, log file's location is relative to the config file.