Red Hat Bugzilla – Bug 237149
killproc returns wrong status code in case where service is already stopped
Last modified: 2014-03-16 23:06:27 EDT
Description of problem:
When doing an /etc/init.d/<service> stop on a stopped service, the script
returns incorrectly $?=1 instead of the correct 0 (per LSB in URL). This is
changed in RHEL5 to the correct behavior.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1./etc/init.d/httpd start (returns 0)
2./etc/init.d/httpd stop (returns 0)
3./etc/init.d/httpd stop (returns 1!)
echo $? returns 1
echo $? should return 0
This causes issues in a clustered environment such as RHCS where the cluster
manager tries to stop the service and gets a failed error code and refuses to
continue. You must manually bring up the service (so that the stop returns a 0)
before being able to re-enable the clustered service.
Correct. However, this is a behavior change that could affect existing scripts,
so the decision was made to not change this for RHEL 4.
*** This bug has been marked as a duplicate of 151104 ***