supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Clemens Fischer" <ino-qc@spotteswoode.de.eu.org>
Subject: Re: runsv and process groups
Date: 26 Aug 2004 18:27:25 +0200	[thread overview]
Message-ID: <6575lv98.fsf@ID-23066.news.dfncis.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0408231722160.5131-100000@e-smith.charlieb.ott.istop.com> (Charlie Brady's message of "Mon, 23 Aug 2004 17:29:32 -0400 (EDT)")

* 2004-08-23 Charlie Brady:

> On 23 Aug 2004, Clemens Fischer wrote:
>
>> 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?

for me this is about choice, but you certainly have a point.  AFAIC i
prefer the current way and advice in the runsv(8) documentation to add the
"chpst -P ..." bit for the "default case".

  clemens


  reply	other threads:[~2004-08-26 16:27 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 [this message]
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=6575lv98.fsf@ID-23066.news.dfncis.de \
    --to=ino-qc@spotteswoode.de.eu.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).