You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Actually, it looks like error_logsupports a special value, stderr to send directly to standard error. Though I think access_log still needs to point at /dev/stdout.
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: