Doc: clarify logfile description #8013
Merged
Conversation
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
The traffic_manager and traffic_server stdout and stderr streams can be bound via the --bind_stdout and --bind_stderr command line options. If this is done, then `proxy.config.output.logfile` can be used to identify that path for log rolling. This change clarifies that the latter configuration is only for log rolling configuration identification purposes and that the filename that ATS uses is actually set via the --bind options. --- This fixes: apache#6249
Contributor
Author
|
This is a doc-only clarification that applies to the 9 release branches as well as master, so marking for those branches as well. Looking through the 8.1.x docs, this doesn't apply to that branch, so not marking it for 8.1.x. |
randall
approved these changes
Jun 29, 2021
zwoop
pushed a commit
that referenced
this pull request
Jul 13, 2021
The traffic_manager and traffic_server stdout and stderr streams can be bound via the --bind_stdout and --bind_stderr command line options. If this is done, then `proxy.config.output.logfile` can be used to identify that path for log rolling. This change clarifies that the latter configuration is only for log rolling configuration identification purposes and that the filename that ATS uses is actually set via the --bind options. --- This fixes: #6249 (cherry picked from commit 534c8b3)
zwoop
pushed a commit
that referenced
this pull request
Jul 13, 2021
The traffic_manager and traffic_server stdout and stderr streams can be bound via the --bind_stdout and --bind_stderr command line options. If this is done, then `proxy.config.output.logfile` can be used to identify that path for log rolling. This change clarifies that the latter configuration is only for log rolling configuration identification purposes and that the filename that ATS uses is actually set via the --bind options. --- This fixes: #6249 (cherry picked from commit 534c8b3)
Contributor
|
Cherry-picked to v9.0.x branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The traffic_manager and traffic_server stdout and stderr streams can be
bound via the --bind_stdout and --bind_stderr command line options. If
this is done, then
proxy.config.output.logfilecan be used to identifythat path for log rolling. This change clarifies that the latter
configuration is only for log rolling configuration identification
purposes and that the filename that ATS uses is actually set via the
--bind options.
This fixes: #6249