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
nice?)


On Sun, Dec 20, 2009 at 2:53 PM, Peter Leonov <gojpeg@gmail.com> wrote:
> On 20.12.2009, at 19:50, Vinay Y s <lists@ruby-forum.com> wrote:
>
>> Gabri Mate wrote:
>>>
>>> Hey There!
>>>
>>> Is there any chance to be able to log access through syslog? It would be
>>
>> 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
>> daemontools.
>>
>> 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 on
> heavu loadef system.
>
> Do not be afraid to use such a configuration :)
>
> Best regards,
> Peter.
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>

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