-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log directly to stdout/stderr #112
Comments
Oh my, I was just looking for this! Please, make it happen, @mars! (Also, 👋 Hi Mars! Hope you're doing well.) |
Actually, it looks like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With everything else set per the solo config example, the following changes make Nginx log directly to stdout/stderr without intermediate filesystem writes & reads as well as no longer needing the multi-process handing in the start-up script:
This change would eliminate traffic-induced filesystem IO and eliminate filesystem consumption by logs.
Would these changes be welcome? To avoid breaking existing usages, we could offer them as a another option of start-up process, and example
config/nginx.conf.erb
.The text was updated successfully, but these errors were encountered: