On Tue, Aug 29, 2006 at 11:18:34AM -0400, Lon Hohberger wrote: > According to the LSB, init scripts are supposed to return 0 in > stop-after-stop situations. Which is not the case at this moment, as bug #151104, that you refer to yourself, already mentions. > Disabling (e.g. failed->disabled) should always work, even if a portion > of the 'stop' phase returns nonzero. It's really the only way to get a This is definitely not the case at this moment. > service out of the failed state - so the assumption is that you have > cleaned up (or will clean up) the service before you try to enable it > again. > > If this is not working, please file a bugzilla -- failed->disable should > work (maybe it should throw better warnings). Will do so. Against rgmanager? > The patch included in the above bugzilla should fix the problem for most > Red Hat (CentOS, etc.) installations, but will not be shipped in any > updates of RHEL4 because of the fact that users / administrators might > be erroneously relying on the "stop after stop returning failure" > "feature" (even though it is not LSB compliant). OK, understood. -- -- Jos Vos <jos@xxxxxx> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
