-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Package: rsyslog Version: 3.18.6-4 Severity: normal
The manpage for rsyslogd says the daemon's pid file is /var/run/syslogd.pid, but it is actually /var/run/rsyslogd.pid. - From the rsyslogd(8) manpage: "Rsyslogd reacts to a set of signals. You may easily send a signal to rsyslogd using the following: kill -SIGNAL $(cat /var/run/syslogd.pid) Note that -SIGNAL must be replaced with the actual signal you are try‐ ing to send, e.g. with HUP. So it then becomes: kill -HUP $(cat /var/run/syslogd.pid)" Observed on a Debian lenny system: r...@debian-lenny:/var/log$ ls -l /var/run/*syslog* - -rw-r--r-- 1 root root 5 2009-05-02 16:04 /var/run/rsyslogd.pid I actually think that it would be better for rsyslogd to use /var/run/syslogd.pid for its pid file, as that would be compatible with scripts written for the old sysklogd that used things like: kill -HUP `cat /var/run/syslogd.pid` To force the daemon to reload its config files. But whatever the pidfile's name, the manpage should be consistent with the actual behaviour. I'm running Debian Lenny on i386 with kernel 2.6.26-2-686. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ/GS0y4enOlZ7nzoRAiBuAKCfC9qMQhFuRbpr09ZV1N+HGjXy0QCg7zVV l/zHLYN+JApVKaJre0LzUHY= =/zjC -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
