Welcome! Log In Create A New Profile

Advanced

Re: Syslog

root@codepedia.eu
April 26, 2012 09:52AM
On 26/04/2012 15:22, Valentin V. Bartenev wrote:
> http://trac.nginx.org/nginx/ticket/95
>
> wbr, Valentin V. Bartenev
I saw that patch, and I understand that syslog(3) does block, but since I need
to set one program identifier per vhost, I wouldn't be using syslog(3), but
rather reimplementing it (already done, taken a lot from glib, bsd license).

Using udp connections would make the call non-blocking, and should be safe
enough on localhost.

Then again, other solutions can be found, such as having a dedicated thread send
the message to syslog, so that logging calls are non-blocking.

Or I could write on a fifo buffer/file the messages and have the dedicated
thread send the messages to syslog (date is set on the sent message, not at the
time the message arrives to syslog, so no problem with that).

Luke

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Syslog

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: 114
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