Christian Engelmayer 8de2e42201 syslogd: work around rename() not renaming hardlinks to themselves ... Function log_locally() within the syslogd can potentially lock up when restarting the daemon after a power loss in case the unplanned shutdown hit the rename operation during logfile rotation. While POSIX requires the rename operation to be atomic, many file systems such as JFFS2 implement the rename operation in 2 steps by linking the new name followed by unlinking the original name. In case of a power loss during the rename the system can end up with /var/log/messages and /var/log/messages.0 being 2 hard links to the same file. When the syslog daemon restarts in such a situation it will rediscover the need to rotate the log files, however, POSIX also requires that rename does nothing and reports success in case oldpath and newpath are existing hard links to the same file. Looping through reopen: by (O_CREAT | O_APPEND), the daemon eternally reopens the same file without succeeding to rotate. Signed-off-by: Christian Engelmayer <christian.engelmayer@frequentis.com> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>		2011-10-28 18:12:42 +02:00
..
Config.src
Kbuild.src
klogd.c
logger.c
logread.c
syslogd_and_logger.c
syslogd.c	syslogd: work around rename() not renaming hardlinks to themselves	2011-10-28 18:12:42 +02:00