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
nginx_syslog_patch in upstream? #6
Comments
You can see the reason here: http://forum.nginx.org/read.php?2,225811,225822#msg-225822 |
Reading that thread, it sounds like FUD, no? Using rsyslogd, whether it is up or not, you can write to /dev/log. The only way to block the write is to suspend the rsyslogd thread... Plus, why couldn't this be made into a ./configure option and let users choose whether they want it or not? Anyway, I'll be testing nginx + syslog patch + rsyslogd. If the results are positive I'll ping the mailing list and ask them to reconsider. |
Thanks. If you want to have a try, we have supported syslog in our nginx fork: http://tengine.taobao.org/index.html . We have implemented syslog protocol internally which don't block the socket at all. |
syslog is included in nginx plus (per http://nginx.com/products/) I'll be annoying on the official tracking bug again: http://trac.nginx.org/nginx/ticket/95 |
as soon as it lets me log in again. |
Could you try tengine(http://tengine.taobao.org/document/http_log.html)? It supports syslog natively. I'm now one of developer of tengine. |
If be happy to! We're mostly using nginx for passenger. Does it support passenger out of the box?
|
I was wondering; will this patch make it upstream eventually?
What is preventing including this in the main nginx?
Seems rather useful!
The text was updated successfully, but these errors were encountered: