I ran into the same problem described in this bug report, but I
diagnosed it as a problem with my system configuration. The syslog-ng
package is not at fault.
The problem I found was that in my system, the bootclean script (part
of the initscripts package) was being started at priority 20 in
runlevel 2 (the rc2.d directory). This script removes files contained
in /var/run (such as syslog-ng.pid), and is intended only for very
early in the boot process. The syslog-ng package is especially
impacted because in a system boot where bootclean is being invoked in
runlevel 2, syslog-ng would have just created its PID file at priority
10 when the bootclean script blows it away. The initscripts package
does not install bootclean in run level 2; it is likely that the
system admin did something to install it. For more background, please
see bug #421195.
Note that in the two directory listings of the two users reporting
this bug, you can see S20bootclean in the /etc/rc2.d directory.
Executing the following command will fix the problem:
update-rc.d -f remove bootclean
The bootclean script is run indirectly by a couple of other scripts
started in runlevel S, so it never needs to be installed directly.
Mike McCallister
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
