2 Feb
2011
2 Feb
'11
2:42 p.m.
On Wed, 2011-02-02 at 17:29 +0300, Mailing Lists wrote:
Not sure if syslog-ng has a bug tracker, but I couldn't find one anyway, so posting this here.
We have a bugzilla at http://bugzilla.balabit.com/ (although I agree, it could be more visibly advertised that it exists), for future reference.
Here is the problem: I have source file that is a log file that is been truncated periodically (by log rotate). When the truncation happens syslog-ng process starts taking 100% CPU, and not doing any logging. This behavior remains until source file receives a write.
This sounds very, very familiar to me. May I ask what platform this is on (OS, architecture, etc)? -- |8]