Re: Checking init.d script for policy compliance.

[Bill Allombert <allomber@math.u-bordeaux.fr>]

On Wed, Apr 02, 2003 at 08:31:19PM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 02 Apr 2003, Bill Allombert wrote:
> The best you can get right now is the work I did on that paper for
> Debconf... It is in http://people.debian.org/~hmh/

Thanks for the pointer. Very interesting!

> I recall something about the LSB status codes not working well with Debian
> as-is.  
> 
> > http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/iniscrptact.html
> > 
> > Here a small extract, but please read it completly:
> > 
> >           In addition to straightforward success, the following situations
> >    are also to be considered successful:
> > 
> >      * restarting a service (instead of reloading it) with the "force-reload"
> >        argument
> > 
> >      * running "start" on a service already running
> > 
> >      * running "stop" on a service already stopped or not running
> > 
> >      * running "restart" on a service already stopped or not running
> 
> These are fine.  But that doesn't mean the rest is. Argh, I need to find
> some time to recheck this init script stuff and update the paper...

Would you second (or better write) a policy proposal documenting
zero/non-zero exit status in all this situations ?

Cheers,
-- 
Bill. <ballombe@debian.org>