Package: lsb-base Version: 3.2-22 Severity: normal User: [email protected] Usertags: initd-status-support
The end user manifestation of this problem is for example in hal, when you run /etc/init.d/hal status as non-root user. (I think supporting running status as non-root is desirable or should at least behave sanely.) Because the PID file in in /var/run/hald/hald.pid (for better or worse), it cannot be read and one cannot even find out whether it exists. So the answer is: hald is not running failed! (exit 3) while hal is running fine. I think a better behavior here would be to do something like could not access PID file "/var/run/hald/hald.pid" (exit 4) or something along those lines. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
