From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: runsv and process groups
Date: Thu, 26 Aug 2004 16:57:54 -0400 [thread overview]
Message-ID: <m3zn4hwr9z.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <20040826204817.1893.qmail@a4750aef5ce996.315fe32.mid.smarden.org> (Gerrit Pape's message of "Thu, 26 Aug 2004 20:48:13 +0000")
Gerrit Pape <pape@smarden.org> wrote:
> Once setsid() is called there's no way back.
But there is after setpgid().
> 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. If
you want to allow all processes to be in the same group, then you need
an option to turn off all changing of process groups, and it doesn't
matter where the change happens when it is enabled. If you want to
allow one service to be in the process group with runsvdir and all the
runsvs, then the change can only happen for the run script, not runsv,
and the script change change its process group back to that of its
parent (setpgid(0, getpgid(getppid()))), perhaps with a new chpst
operation.
paul
next prev parent reply other threads:[~2004-08-26 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 17:30 getty trouble Dan Melomedman
2004-08-20 7:19 ` Gerrit Pape
2004-08-20 16:45 ` Dan Melomedman
2004-08-23 0:04 ` runsv and process groups (was Re: getty trouble) Charlie Brady
2004-08-23 13:26 ` runsv and process groups Clemens Fischer
2004-08-23 21:29 ` Charlie Brady
2004-08-26 16:27 ` Clemens Fischer
2004-08-26 17:05 ` Charlie Brady
2004-08-26 20:48 ` Gerrit Pape
2004-08-26 20:57 ` Paul Jarc [this message]
2004-08-29 9:39 ` Gerrit Pape
2004-08-27 1:06 ` Charlie Brady
2004-09-11 9:58 ` Gerrit Pape
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zn4hwr9z.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).