<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>----- Original message -----
<br>> Balazs Scheidler <<a href="mailto:bazsi77@gmail.com">bazsi77@gmail.com</a>> writes:
<br>>
<br>> > no need to use inotify for this. merely stating the file regularly
<br>> > should indicate the new file with a changed inode number.
<br>>
<br>> But inotify has the benefit of not needing regular polls, and immediate
<br>> notification when files change. I wouldn't want it for performance,
<br>> because it wouldn't give a noticable boost in this case. I like inotify
<br>> better in this case because of responsiveness, and effectiveness.
<br>>
<br>> For example, if my low-power system is happily idling, I'd rather not
<br>> have syslog-ng regularly stat files and wake up the disk. However, if
<br>> the kernel signals us that hey, this stuff here changed, that's much
<br>> more efficient.
<br>>
<br>> Sadly, I don't have such a system where it would make any difference,
<br>> but still! :P
<br>
<br>sorry I may have put that a bit easy to misunderstand. I meant that we can issue a stat before each write. No need to start separate polling. Syslog-ng has woken up in that case anyway.
<br>
<br>>
<br>> > i was thinking about a separate operation to reopen files
<br>> > (e.g. syslog-ng-ctl reopen-files) to avoid having to reload the
<br>> > configuration, but this idea seems simpler to implement.
<br>>
<br>> syslog-ng-ctl reopen-files could be useful nevertheless, for different
<br>> purposes.<br></p>
</body>
</html>