CPU. I find that when the usage is that high it doesn't log at all, if so just the occasional log.
If I leave it, it ends up using 99% :-( I don't think it's my syslog-ng.conf that's doing it as it's fairly generic.
I haven't had it start taking up CPU yet, but it sure leaks memory like a seive.
Sounds like a great program...loads CPU even when inactive, and eats up all available memory within a couple of weeks on a machine otherwise mostly unused. Hmm, sounds like Netscape ;)
Unfortunately, syslog-ng's ability to do TCP logging, unlimited forwarding, and the nice log-by-host/program makes it an invaluable tool, so it's worth fixing rather than abandoning.
Does the author read the list? Respond well to patches? The code isn't too huge, I might try to find the leak myself.
I'm the author, and I host this list so obviously I read it sometimes. Things were quite rough here nowadays, so I couldn't do anything useful on syslog-ng. However I know about the problem so a fix will be available ASAP. (whatever this means) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt