<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#0050d0">
<font size="-1"><font face="Helvetica, Arial, sans-serif">VI doesnt do
that though</font></font><font size="-1"><font
face="Helvetica, Arial, sans-serif"> (would wreak havoc with selinux
and others if it did), n</font></font><font size="-1"><font
face="Helvetica, Arial, sans-serif">ot unless you have some uncommon
vi settings. It might cause a problem if vi opens the file, the file
grows while its open, and so when its written out, it basically gets
truncated back. At that point syslog-ng would be trying to write past
where the actual end of the file is. I've never messed with such
situations, so I'm not sure what the effect of that is.<br>
<br>
-Patrick<br>
</font></font><br>
Sent: Fri Jan 28 2011 01:00:00 GMT-0700 (Mountain Standard Time)<br>
From: Fegan, Joe (CSBU) <a class="moz-txt-link-rfc2396E" href="mailto:Joe.Fegan@hp.com"><Joe.Fegan@hp.com></a><br>
To: Syslog-ng users' and developers' mailing list
<a class="moz-txt-link-rfc2396E" href="mailto:syslog-ng@lists.balabit.hu"><syslog-ng@lists.balabit.hu></a> <br>
Subject: Re: [syslog-ng] A known syslog-ng issue/bug?
<blockquote
cite="mid:0E6222894DE49B40A3A9FD929C630BCB66D0D28140@GVW1121EXC.americas.hpqcorp.net"
type="cite">
<pre wrap="">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: <a class="moz-txt-link-abbreviated" href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a> [<a class="moz-txt-link-abbreviated" href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a>] On Behalf Of Xuan Zhong [<a class="moz-txt-link-abbreviated" href="mailto:xuan_zhong@hotmail.com">xuan_zhong@hotmail.com</a>]
Sent: 27 January 2011 20:49
To: <a class="moz-txt-link-abbreviated" href="mailto:syslog-ng@lists.balabit.hu">syslog-ng@lists.balabit.hu</a>
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
______________________________________________________________________________
Member info: <a class="moz-txt-link-freetext" href="https://lists.balabit.hu/mailman/listinfo/syslog-ng">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
Documentation: <a class="moz-txt-link-freetext" href="http://www.balabit.com/support/documentation/?product=syslog-ng">http://www.balabit.com/support/documentation/?product=syslog-ng</a>
FAQ: <a class="moz-txt-link-freetext" href="http://www.campin.net/syslog-ng/faq.html">http://www.campin.net/syslog-ng/faq.html</a>
</pre>
</blockquote>
</body>
</html>