* Joan Picanyol i Puig writes:
> * Lasse Kliemann <lasse-list-supervision-2007@plastictree.net> [20071010 14:57]:
> > I'd like to run a bunch of services in a kind of sub-hierarchy under 
> > `/service/sub'; more precisely the service in `/service/sub' shall be something 
> > like runsvdir managing services in a directory `/service/sub/service'.
> > 
> > The naive approach was to let `/service/sub/run' be like this:
> > 
> >    #!/bin/sh
> >    exec runsvdir service
> > 
> > One problem with this is that bringing down all services in 
> > `/service/sub/services' involves something like
> > 
> >    sv o /service/sub ; sv h /service/sub
> 
> What's wrong with 'sv h /service/sub/services/*' ?
 
Howsoever, neither of the two solutions yields an elegant way to make this 
work *inductively* starting from the 'root' runsvdir process in /service.

Well, one could place

   sv x ./service/*

in /service/sub/finish.

> http://cr.yp.to/daemontools/svscan.html
> "svscan is designed to run forever."
>
> The same applies to runsvdir; if you need to stop it, you are doing
> something wrong.

Can this reasonably be applied to any runsvdir (or svscan) process other than 
the 'root' one?