On Wed, Oct 24, 2007 at 01:30:08AM -0400, Lauro, John wrote:
>
> > BTW Malcolm, be careful, the default syslogd from sysklogd cannot
> forward
> > messages to a remote syslog server if it received them from a UDP
> socket.
> > This is pretty annoying because syslogd is slow on disk and cannot
> forward.
> > If you want to use this solution in your appliances, I strongly
> suggest
> > that you switch to another syslogd.
> >
>
> syslogd isn't so bad if you prefix the busy log filename with a -. By
> default syslogd causes a fsync after every message, but as long as you
> let it buffer by using a - it's fairly efficient on disk.
I know, but I never got it to log more than 300 lines/s without randomly dropping some of them, and eating all the CPU. On some systems, I need 10000 lines/s with very few CPU eaten.
Regards,
Willy
Received on 2007/10/24 08:50
This archive was generated by hypermail 2.2.0 : 2007/11/04 19:21 CET