bneradt commented on issue #6249: URL: https://github.com/apache/trafficserver/issues/6249#issuecomment-870735089
Yes, I happened to just come across this code while working on #7937. Our documentation is a bit misleading about `proxy.config.output.logfile`. It currently, it says: https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html?highlight=proxy.config.output.logfile#proxy.config.output.logfile > The name and location of the file that contains warnings, status messages, and error messages produced by the Traffic Server processes. If no path is specified, then Traffic Server creates the file in its logging directory. This is mostly true, in a very literal sense. But most readers will read this as implying that this becomes the name of the file that gets created by the ATS process for stdout/stderr logs. In fact, this is not how this configuration works. The name of the stdout/stderr file is set, as you observed, via `--bind_stdout` and `--bind_stderr` arguments to the process. The `proxy.config.output.logfile` isn't used to set the name of the file, but to configure ATS concerning what the file was named via these command line parameters for the purpose of log rotation. If you configure `proxy.config.output.logfile` differently than `--bind_stdout` and `--bind_stderr` then log rotation of that file will not work. Thus, to restate this: * The name of the file ATS creates and writes to for process output is set via `--bind_stdout` and `--bind_stderr` command line parameters. * If you want that output file to be rotated by the ATS process, you have to separately tell ATS what the name of the file you set on the command line with `--bind_stdout` and `--bind_stderr` via the `proxy.config.output.logfile` records.config parameter. I'll update the docs to make this clearer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
