Welcome! Log In Create A New Profile


Re: Syslog

April 26, 2012 10:34AM
On 26/04/2012 16:03, Maxim Dounin wrote:
> Hello!
> The main problem with syslog in general is that it's interface
> blocks, and if syslogd daemon is dead/can't cope with load nginx
> won't be able to work. Additionally, it's slow/resource
> consuming. Writing normal files is much faster and more reliable.
> Given the above, it's highly unlikely that syslog patches of any
> quality will be accepted.
> Maxim Dounin
Thank you for your reply, but as I said, I already have reimplemented syslog(3),
and with the aid of a udp or fifo with a thread things can be made completely
Or I could use an aio_write() instead of a write() to write to the local syslog
socket, although a fifo is more secure for syslog crashes/hangups (which I've
never seen, anyway).

Anyway, let's assume for a second that I can get file-like performance.
The questions that remains are 2:
1- What format do you like more? I'm inclined towards something like
"syslog_access ident:facility:priority:host:port:connectiontype"
2- How should I benchmark it all?


nginx mailing list
Subject Author Posted


Luke April 26, 2012 09:16AM

Re: Syslog

Valentin V. Bartenev April 26, 2012 09:24AM

Re: Syslog

root@codepedia.eu April 26, 2012 09:52AM

Re: Syslog

Maxim Dounin April 26, 2012 10:04AM

Re: Syslog

Luke April 26, 2012 10:34AM

Re: Syslog

dlang July 15, 2012 05:57PM

Re: Syslog

姚伟斌 July 16, 2012 01:46AM

Re: Syslog

splitice July 28, 2012 09:36PM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 106
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready