On Tue, 2006-08-29 at 22:49 +0200, Jos Vos wrote: > 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? Yes. I'm pretty sure this works, but maybe there's something about your configuration in particular which is preventing it from working. So, if you could include it (the service blob -- stuff in the <rm> tag), that would be great. -- Lon -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
