Re: Checking init.d script for policy compliance.
On Wed, 02 Apr 2003, Bill Allombert wrote:
> On Wed, Apr 02, 2003 at 06:49:11PM +0100, Colin Watson wrote:
> > On Wed, Apr 02, 2003 at 04:55:32PM +0200, Bill Allombert wrote:
> > > Wrong exit status when stopped but not running
> > > inetd lpd nfs-common portmap ssh *pdnsd *exim *gpm *lprng
> >
> > I'd like to fix ssh, but I can't find the policy on init scripts' exit
> > statuses. Can you point me to it, please?
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/
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...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: