----- Original message -----
Balazs Scheidler <bazsi77@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.
For example, if my low-power system is happily idling, I'd rather not have syslog-ng regularly stat files and wake up the disk. However, if the kernel signals us that hey, this stuff here changed, that's much more efficient.
Sadly, I don't have such a system where it would make any difference, but still! :P
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.
i was thinking about a separate operation to reopen files (e.g. syslog-ng-ctl reopen-files) to avoid having to reload the configuration, but this idea seems simpler to implement.
syslog-ng-ctl reopen-files could be useful nevertheless, for different purposes.