On Sat, Jan 23, 2010 at 12:59 PM, Willy Tarreau <[email protected]> wrote: > it may happen depending on the load, your syslog daemon and its config. > The syslog daemon from the sysklogd package is generally OK up to 1000 > logs per second on recent, and will start dropping some of them above. > However, it is important to note that this syslogd does synchronous > logging by default, which reduces its potential to only a few tens of > logs per second. You have to prepend a "-" sign in front of the log > file names to disable this feature, like this : > > local0.* -/var/log/haproxy.log
Ah, our logging was set to be synchronous. That's what happens when you outsource your server management. Thanks! > With a properly tuned syslog-ng server, you can generally log > 10-20000 logs per second without any loss. What tuning options are available for syslog-ng that I should consider?
