Am 28.02.2011 14:52, schrieb Michael Prokop: > # /etc/init.d/rsyslog status > could not access PID file for rsyslogd ... failed! > # echo $? > 4 > # ls -la /lib/init/rw/sendsigs.omit.d/rsyslog > lrwxrwxrwx 1 root root 21 Feb 28 14:48 /lib/init/rw/sendsigs.omit.d/rsyslog > -> /var/run/rsyslogd.pid > # ls -la /var/run/rsyslogd.pid > ls: cannot access /var/run/rsyslogd.pid: No such file or directory > > Hm? I'd expected to get exit code "3" instead: >
I can not reproduce this problem here. If rsyslog is not running and there is no /var/run/rsyslogd.pid: # /etc/init.d/rsyslog status rsyslogd is not running ... failed! # echo $? 3 If there is a dangling symlink /lib/init/rw/sendsigs.omit.d/rsyslog there is the same exit code. So, maybe your system is probably really in an unknown state :-) That said, rsyslog uses the status_of_proc() method from /lib/lsb/init-functions (lsb-base). If you think the reported status code is wrong, it's best to discuss that with the lsb-base maintainers. Could you investigate, why status_of_proc() returns 4 in your case? Feel free to reassign, otherwise I'm going to close this bug report against rsyslog. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
