On Tue, Sep 14, 2004 at 11:14:20PM +0200, Stefan Hornburg wrote: > > Letting such a check be implemented by the maintainers would at least be > > better than seeing watchdog scripts that just check for strings in the > > process list or similar things which seem to work just as long as it's not > > needed. > > One idea would be some kind of exit code list > > 100 - up and running > > 110 - up but not responding correctly > > 111 - down > > 112 - administrativly wanted to be down > > Another some kind of machine readable first line. > Why not using codes like common protocols (HTTP, SMTP), where the > first number is the general idea about the state, like 2xx for HTTP > success. /etc/init.d/foo status would return e.g. > 200 Up and Running (exit code 0) > I suggest to use exit codes != 1 only if the init script itself is broken. Please compare with what the LSB already has to say about init script arguments and return values before engaging in an NIH foray. -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature