[syslog-ng] A known syslog-ng issue/bug?

[Fegan, Joe (CSBU)]

This sounds like a standard Linux/Unix problem - a program has a file open and is actively writing to it. I open the file in vi and do "save". What actually happens is that vi unlinks the existing file and writes a completely new file that happens to have the same name. The program continues to write to the unlinked file (which is a perfectly valid thing to do in Linux/Unix).

________________________________
From: syslog-ng-bounces at lists.balabit.hu [syslog-ng-bounces at lists.balabit.hu] On Behalf Of Xuan Zhong [xuan_zhong at hotmail.com]
Sent: 27 January 2011 20:49
To: syslog-ng at lists.balabit.hu
Subject: [syslog-ng] A known syslog-ng issue/bug?

Hi,

This issue is that if someone looks at a log file generated by syslog-ng with vi, and then “accidentally” writes and saves the file, subsequent writes to the file by syslog-ng don’t appear to work.  If syslog-ng closes the file (which happens if it is “idle” for a configurable period, whose default is 1 minute), and then re-opens it when it next needs to write, the writes succeed. Similarly, “service syslog-ng reload” (or restart) will clear the problem.

Anyone experienced the similar problem?

Thanks
Xuan