Re: loggint through syslog - Michael Shadle - ru.sysoev.nginx

14 messages in ru.sysoev.nginxRe: loggint through syslog

From	Sent On	Attachments
Gabri Mate	Dec 16, 2009 1:52 pm
merlin corey	Dec 17, 2009 2:23 pm
Ryan Malayter	Dec 17, 2009 4:41 pm
merlin corey	Dec 17, 2009 4:56 pm
Ryan Malayter	Dec 17, 2009 9:33 pm
merlin corey	Dec 18, 2009 5:13 pm
Ryan Malayter	Dec 19, 2009 7:03 pm
Vinay Y s	Dec 20, 2009 8:49 am
Peter Leonov	Dec 20, 2009 2:52 pm
Michael Shadle	Dec 20, 2009 2:56 pm
Kingsley Foreman	Dec 20, 2009 3:04 pm
Michael Shadle	Dec 20, 2009 3:10 pm
merlin corey	Dec 21, 2009 5:15 pm
Ryan Malayter	Dec 23, 2009 6:45 pm

Subject:	Re: loggint through syslog
From:	Michael Shadle (mike...@gmail.com)
Date:	Dec 20, 2009 2:56:11 pm
List:	ru.sysoev.nginx

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 <goj...@gmail.com> wrote:

On 20.12.2009, at 19:50, Vinay Y s <lis...@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 :)

	Start a set with this search
	Include this search in one of my sets
	Exclude this search from one of my sets