From: Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: runsv and process groups
Date: Mon, 23 Aug 2004 17:29:32 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0408231722160.5131-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <1xhyvvbx.fsf@ID-23066.news.dfncis.de>
On 23 Aug 2004, Clemens Fischer wrote:
> * Charlie Brady:
>
> > Can you think of any reason why runsv *shouldn't* make the supervised
> > process a process group leader? It'd take very little code ...
>
> how about this one: there might be a *vital* service running on the
> machine which you *want* to bring the machine down in case it fails.
How likely is that to be the case? Could that problem only be solved by
keeping the current behaviour?
> with the current behaviour, the user can choose to give it its own session
> using "chpst -P ..." as an additional option.
Sure, but to be safe, you need to do that in every run script. Wouldn't it
be easier for (nearly) everyone if runsv did it?
---
Charlie
next prev parent reply other threads:[~2004-08-23 21:29 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 [this message]
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
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=Pine.LNX.4.44.0408231722160.5131-100000@e-smith.charlieb.ott.istop.com \
--to=charlieb-smarden-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.org \
/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).