[Linux-cluster] Monitoring services/customize failure criteria

Lars Marowsky-Bree lmb at suse.de
Mon Sep 15 08:25:26 UTC 2008

On 2008-09-10T18:58:19, Jeff Stoner <jstoner at opsource.net> wrote:

> The Script resource is a generic resource (as opposed to the more
> specific mysql, nfs, ip, file system, etc. resources.) The script
> identified in the <script> section is responsible for properly starting,
> stopping and verifying the resource is functioning properly. The script
> needs to conform to LSB + OCF RA API draft specifications. This means a
> script *must* accept as parameters, at a minimum for use with cluster
> services, start, stop and status. These script must exit with 0 for
> success and a non-zero value for any non-success condition (error,
> warning, got up on the wrong side of the bed, whatever.)

Is it really only 0 versus non-zero for status? How does the system
distinguish between running, failed, and cleanly stopped then? I ask
because both LSB & OCF specify a slightly more differentiated status
exit code.


Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

More information about the Linux-cluster mailing list