Red Hat Bugzilla – Bug 173991
initscripts not LSB-compliant, breaking cluster suite
Last modified: 2014-03-16 22:57:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.7.12-126.96.36.199
Description of problem:
The initscripts shipped with RHEL4 do not have LSB-compliant behaviour, and therefore break cluster suite.
Clustersuite expects the following behaviour:-
1. If the 'start' method is called when the service is already running, the init script should return success.
2. If the 'stop' method is called when the service is not running, the init scripts should return success.
This is the defined behaviour according to LSB 1.3 (http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/iniscrptact.html)
Example init scripts that do not follow this behaviour:
httpd, smb do not observe behaviour 2.
nsdcd does not observe behaviour 1.
Some scripts (e.g. pam) do seem to be compliant.
This bug is particularly bad as the walkthrough documentation for RHCS at http://www.redhat.com/docs/manuals/csgfs/browse/rh-cs-en/ch-httpd-service.html uses httpd as an example - this will not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. service httpd start
2. service httpd stop
3. service httpd stop
4. echo $?
Actual Results: 1
Expected Results: 0
I'm putting this to a severity of high as it seriously compromises the availability of HA clusters.
Blah, where I say 'some scripts (e.g. pam) seem to be compliant' I meant gpm
*** This bug has been marked as a duplicate of 151104 ***
Note that scripts shipped with the OS are not required to be LSB compliant.
While scripts shipped with the OS are not required to be LSB compliant, our
clients might reasonably expect them to actually work with Red Hat Cluster suite.