Re: Nested runsvdir

[Gerrit Pape <pape@smarden.org>]

On Thu, Sep 16, 2004 at 12:13:50PM -0700, Jared Rhine wrote:
> Are there any known caveats to "nesting" runsvdir instances?  I'm
> having problems with signals and processes reparenting to init.
> 
> By nested I mean that an init-started "main" runsvdir has one service
> which has a run script of:
> 
> -- begin --
> #!/bin/sh 
> exec 2>&1 
> exec chpst -P -u monitor -e /var/di/monitor/runit/envdir runsvdir -P /var/di/monitor/runit/services 'log: ..........'
> -- end --

>               I can start/stop/manipulate these services fine using
> runsvctrl.
> 
> But if I terminate the "parent" service (via runsvctrl down for
> instance), the router and archiver runsv processes don't die; they
> instead move to a parent pid of 1.  I can then runsvctrl the router
> and archiver services fine.  But this is a bad situation to put the
> server in and worse case (except I'm using chpst -L lockfiles), I get
> multiple daemons running.  I expect that killing the nested runsvdir
> should kill all its child services.
> 
> runit is probably doing the expected thing given what I'm thrown at

Yes, see section SIGNALS in runsvdir(8):
       If runsvdir receives a TERM signal, it exits with 0 immediately.

       If runsvdir receives a HUP signal, it sends a TERM signal to each
       runsv(8) process it is monitoring and then exits with 111.

> Suggestions or snippets of working "nested" runsvdir configurations
> would be most appreciated.

I suggest that you run svwaitdown -xk /var/di/monitor/runit/services/*
in the ./finish script of the runsvdir service, just as runit's stage 3
does for the main runsvdir process (stage 2) after it's terminated.
That should fix your problem.

Regards, Gerrit.