Re: runit and lsb init script actions

["Csillag Tamás" <cstamas@digitus.itk.ppke.hu>]

On 04/10, 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.
> 
> What do you think?
> 
> Thanks, Gerrit.

I made similar script as Charlie Brady's, but mine is a bit simpler.

#! /bin/sh

NAME=someservicename

case "$1" in
  start)
        echo -n "Starting $NAME"
        /usr/bin/runsvctrl u /service/$NAME
        echo "."
        ;;
  stop)
        echo -n "Stopping $NAME"
        /usr/bin/runsvctrl d /service/$NAME
        echo "."
        ;;
  restart)
        echo -n "Restarting $NAME"
        /usr/bin/runsvctrl t /service/$NAME
        echo "."
        ;;
  *)
        echo "Usage: $0 {start|stop|restart}" >&2
        exit 1
        ;;
esac

exit 0

I use this one in Debian so if I upgrade, it can start/stop the services as needed.
(As you can see this is a minimalist script.)

The only problem which I see that runit is in /usr/bin and as a base system utility
it should be in /sbin or /bin (like init).

What do you think?

-- 
"Real programmers can write assembly code in any language."
                                              -- Larry Wall

cstamas