On Friday 17 August 2007 4:55 am, Andrew Beekhof wrote:
> > That message is from SUSE's startproc command. It was cupsd that exited
> > with a status of 1. startproc pointed this out, since it checks for start
> > failures and correctly returned 7.
>
> i dont believe that in this particular case 7 is correct.
> at least its not what you want the node to be fenced as a result.
>
> 7 means "the resource is safely stopped"
> use one of:
> * EXECRA_UNKNOWN_ERROR = 1,
> * EXECRA_INVALID_PARAM = 2,
> * EXECRA_UNIMPLEMENT_FEATURE = 3,
> * EXECRA_INSUFFICIENT_PRIV = 4,
> if you want the node shot.
Hrm. According to the startproc(8) man page:
The exit codes have the following LSB conform conditions:
0 Success
1 Generic or unspecified error
2 Invalid or excess argument(s)
4 Insufficient privilege(s)
5 Program is not installed
7 Program is not running
IIRC, startproc calls a daemon process, which will fork and exit, returning an
exit code. If it returns non-zero, startproc will return 1. If the process
returns 0, it checks to see if the daemon is still running. If not, startproc
will return 7.
When I call cupsd manually with the config file missing, it returns 0, but the
child process dies.
> in the mean-time, i have uploaded some new packages which fix the related
> bug.
Cool. Thanks,
--
James Oakley
[EMAIL PROTECTED]
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
