28 Jun
2000
28 Jun
'00
2:51 p.m.
Obviously some kind of significant memory leak. According to the list archives, another poster put up a patch but he has not responded to my inquiries; I'm wondering if anyone else has patches or has used the patch posted not too long ago...or at least, perhaps someone could confirm that they also must restart the syslog-ng process daily to combat memory leakage.
I tend to restart the syslog-ng when ever it starts using over 35% 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. Cheers, John