Re: runsv and process groups

[Gerrit Pape <pape@smarden.org>]

On Thu, Aug 26, 2004 at 04:57:54PM -0400, Paul Jarc wrote:
> Gerrit Pape <pape@smarden.org> wrote:
> > Once setsid() is called there's no way back.
> But there is after setpgid().
Hm, I'm not yet sure about all the implications when changing the
default behavior.

> > Hm, I'm not sure yet.  What do you think about runsvdir running runsv in
> > a new process group, and not runsv the run script?
> 
> It depends what kinds of arrangements you want to make possible.

Primarily I want to address Charlie's concern.  It's true that a buggy
program that kills the process group it didn't create kills the stage 2
runsvdir process, and so causes runit to enter stage 3.  But I think
it's also true that this may be used as a feature as Clement noted; the
runsv and runsvdir programs also can be used independently, and in user
space.  And I don't want to make major changes to the default behavior
of the runit programs in versions 1.0.x.

Having runsvdir create a process group for each runsv process could be
done through a command line option and switched on optionally, it's not
that easy with runsv.  This doesn't solve Dan's trouble with the getty
service though, some getties would still need to be run with chpst -P;
this should be documented.

Thanks for your input, Gerrit.