Re: runit and lsb init script actions

[Gerrit Pape <pape@smarden.org>]

On Sun, Apr 10, 2005 at 01:00:18PM -0400, Charlie Brady wrote:
> On Sun, 10 Apr 2005, Gerrit Pape wrote:
> >Hi, one thing that has been requested for runit multiple times is lsb
> >compliance concerning 'init script' actions, see
> >
> >http://refspecs.freestandards.org/LSB_2.1.0/LSB-Core-generic/LSB-Core-generic.html#INISCRPTACT
> >
> >It seems to be quite possible to implement an lsb compliant interface
> >through a separate program that runs runsvctrl up, down, term, hup, ...,
> >depending on the command line arguments.  For service daemons that don't
> >do the right thing on up, down, term, hup, ..., it's possible to
> >override the actions through the customized control scripts in
> ><service>/control/.  This separate program may be symlinked to
> >/etc/init.d/<service>, or used as a wrapper, and maybe fall back to an
> >original /etc/init.d/<service> script in case the service doesn't run
> >under runit's supervision.

> Here's a runit specific version I use under a RedHat based system:

Yes, this is the link approach, looks good.  I'm still thinking about
the wrapper; Debian uses an invoke-rc.d program to call init scripts on
package installation, which supports a user defined policy.  In any case
this needs documentation, a man page, and maybe an 'lsb init script
actions' page.

> # Determine the service name and its service directory from $0
> 
> SERVICE=$(/bin/basename $0 | sed -e 's/^[SK][0-9][0-9]*//')

SERVICE=${0##*/}
SERVICE=${SERVICE#[SK][0-9][0-9]}

>     *)
>         echo "usage: $0 
>         {start|stop|restart|status|sigalrm|sigcont|sighup|sigint|sigkill|sigstop|sigterm|sigusr1|sigusr2|svdisable}"
>         ;;

I don't think all these options should be supported, just the ones the
lsb documents.  runit services still should be controlled through the
runsvctrl program.

Thanks, Gerrit.