Cool, thanks.
Heh, here's an interesting quote:
"In addition to straightforward success, the following situations are
also to be considered successful: ... running stop on a service already
stopped or not running ..."
This is exactly what I was complaining/asking about a few days ago - the
"stock" httpd init script in RHEL4 returns non-zero if you try to stop
it when it's not running. This in turn causes clusvcadm -d to fail if
you try to disable it when it's not running, so you have to manually
start it "non-clusterfied" before you can disable it in the cluster! I
haven't done a survey, but I'm guessing other scripts behave similarly.
But the spec is self-contradictory, because further down it defines an
error status code for "program is not running" that it says it to be
used for any action other than 'status'!
So ... is this a bug in the script or a "bug" in the document?
-g
Lon Hohberger wrote:
On Wed, 2006-02-01 at 09:57 -0500, Greg Forte wrote:
Never mind, I'm an idiot - none of my scripts support the "status"
command, so of course the resource manager is going to fail them ... ugh.
In my defense, though, I haven't found any documentation describing
minimum requirements for a CS-compatible init script. Does any exist?
Pretty sure any script correctly implementing the LSB-spec for init
scripts should work. Check here:
http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
-- Lon
--
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Greg Forte
gforte@xxxxxxxx
IT - User Services
University of Delaware
302-831-1982
Newark, DE
--
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster