Fix failure to launch Fluentd on Windows with log rotation but not specifying the log path in the command line - #4188
Merged
Conversation
Fix a bug of f8b73a5 (fluent#4091). Before that fix, Fluentd can start if rotation is enabled but the log file path is not specified. After that fix, the logger setup starts to fail on Windows. This fix solves it. Signed-off-by: Daijiro Fukuda <fukuda@clear-code.com>
ashie
self-requested a review
May 29, 2023 06:59
Member
|
Hmm, although it's not a problem of this PR, time out occurs on Ruby head: |
Member
|
Thanks! |
Contributor
Author
|
Thanks for your review! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue(s) this PR fixes:
Fixes #4187
What this PR does / why we need it:
Fix a bug of f8b73a5 (#4091).
Before that fix, Fluentd can start if rotation is enabled but the log file path is not specified.
After that fix, the logger setup starts to fail on Windows.
This fix solves it.
Docs Changes:
Not needed.
Release Note:
Same as the title.