[syslog-ng] [PATCH] make 'syslog-ng -s' stay in the foreground

[Corey Hickey]

Hi,

I recently upgraded to syslog-ng 3.1.1 and noticed messages like this
appearing on terminals owned by root:

2010 May  7 06:25:21 fire Daemon exited gracefully, not restarting;
exitcode='0'

This is triggered by a daily logrotate cron job that runs 'syslog-ng -s'
before sending the daemon a SIGHUP. It seems that 'syslog-ng -s' will
daemonize and fork; the child process runs the syntax check and exits
immediately, and then the parent process sends the above message via
syslog(LOG_CRIT,...).

I can work around it by using 'syslog-ng -sF', but I also hacked up a
small patch to force the process to be in the foreground when -s is
specified. Is this useful? If not, I'll send a patch to Debian to use
'syslog-ng -sF' instead.

Thanks,
Corey
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: syntax_foreground.diff
Url: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20100508/384245f7/attachment.txt