Re: [gentoo-dev] default logger

[Alec Warner]

Mike Frysinger wrote:

>On Tuesday 27 September 2005 02:59 pm, Donnie Berkholz wrote:
>
>
>>Ciaran McCreesh wrote:
>>| Ok, for those who don't remember...
>>|
>>| In the good old days, syslog-ng was the default. Then, for one of the
>>| releases, the x86 team accidentally included metalog instead of
>>| syslog-ng on the distfiles CD, so the default was changed over to make
>>| the x86 networkless install documentation work (at the expense of the
>>| archs that got it right). So, it's not a case of moving away from
>>| metalog at all, it's a case of undoing a temporary change.
>>
>>In the bad old days, metalog was the default. Then it got switched to
>>syslog-ng because people got confused as hell by metalog's buffering,
>>and there was no reason not to use a more capable logger that's
>>compatible with the traditional sysklogd, minus the annoying feature of
>>metalog.
>>
>>
>
>ok, i thought that's how *i* remembered it :)
>
>
>
>>FWIW, I think metalog's buffering disappeared a while back, at least by
>>default.
>>
>>
>
>yes, default metalog config file is unbuffered (and has been for a while), and
>the init script lets you switch between modes now on the fly so you dont have
>to send the kill signals yourself.  whether it's 'annoying' is certainly a
>matter of opinion :P, but from a technical aspect, buffering makes a lot of
>sense if the performance matters.
>-mike
>
>
I think syslog-ng is a better logger, except the default configuration 
is pretty icky.  I would shoot for something better, even if it's in 
/usr/share.  I heard hardened's config is quite nice :)  At least 
provide an example of a config that sorts logging out into seperate 
files like most distro's do.
-- 
gentoo-dev@g.o mailing list