loggint through syslog
kingsley at internode.com.au
Mon Dec 21 02:04:47 MSK 2009
i would like an official syslog patch also, or at least an option say
error_log syslog:info crit;
or something like that.
From: "Michael Shadle" <mike503 at gmail.com>
Sent: Monday, December 21, 2009 9:26 AM
To: <nginx at nginx.org>
Subject: Re: loggint through syslog
> I'd still be +1 for a syslog module/patch to be official
> If there's a way to fire off the message and forget about it so it
> doesn't block, then I don't see a problem (I wouldn't recommend it for
> access logging necessarily, but for error logging and such it would be
> On Sun, Dec 20, 2009 at 2:53 PM, Peter Leonov <gojpeg at gmail.com> wrote:
>> On 20.12.2009, at 19:50, Vinay Y s <lists at ruby-forum.com> wrote:
>>> Gabri Mate wrote:
>>>> Hey There!
>>>> Is there any chance to be able to log access through syslog? It would
>>> I doubt if there is built-in support for logging to syslog directly. But
>>> you can achieve something almost as good by simply tailing the logs to
>>> the syslog logger command.
>>> try this:
>>> tail -f access.log | logger -p local5.err -t nginx
>>> you can ensure this is always running by using something like
>>> Surely this will have worser performance than if it were implemented
>>> natively within nginx.
>> The recent descussion in the Russian list tells the opposite. Performance
>> may become even better due to packet nature of the network: less packets
>> heavu loadef system.
>> Do not be afraid to use such a configuration :)
>> Best regards,
>> nginx mailing list
>> nginx at nginx.org
> nginx mailing list
> nginx at nginx.org
More information about the nginx