[syslog-ng] feature request?: monitor open logs for deletion/rename

Patrick Hemmer syslogng at stormcloud9.net
Thu Jul 12 13:59:01 CEST 2012

Sent: Thu Jul 12 2012 06:12:11 GMT-0400 (EDT)
From: Sandor Geller <Sandor.Geller at morganstanley.com>
To: Syslog-ng users' and developers' mailing list 
<syslog-ng at lists.balabit.hu>
Subject: Re: [syslog-ng] feature request?: monitor open logs for 
> On Thu, Jul 12, 2012 at 11:40 AM, Gergely Nagy<algernon at balabit.hu>  wrote:
>> Balazs Scheidler<bazsi77 at gmail.com>  writes:
>>> no need to use inotify for this. merely stating the file regularly
>>> should indicate the new file with a changed inode number.
>> But inotify has the benefit of not needing regular polls, and immediate
>> notification when files change. I wouldn't want it for performance,
>> because it wouldn't give a noticable boost in this case. I like inotify
>> better in this case because of responsiveness, and effectiveness.
> inotify works only on local filesystems - so you'll either end up
> adding some complexity (syslog-ng needs to check that a given
> destination file is on a local fs or on a remote one) or should use an
> existing framework having FAM-like functionality. glib has gio for
> such purpose, right?
Actually inotify does work on network filesystems, but it just cant know 
when a remote host updates the file, only the local host. But nobody 
ever has multiple hosts writing to the same network file at the same 
time, right? Right?
Just kidding, I know out there someone is going to be doing something 
evil like that.


More information about the syslog-ng mailing list