supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Cc: Jared Rhine <jared@wordzoo.com>
Subject: Re: Nested runsvdir
Date: Sun, 19 Sep 2004 20:02:40 +0000	[thread overview]
Message-ID: <20040919200236.28026.qmail@32044832572666.315fe32.mid.smarden.org> (raw)
In-Reply-To: <20040917024546.GD11101@tinyvaio.nome.ca>

On Fri, Sep 17, 2004 at 11:45:49AM +0900, mike@mikebell.org wrote:
> On Thu, Sep 16, 2004 at 12:13:50PM -0700, Jared Rhine wrote:
> > Are there any known caveats to "nesting" runsvdir instances?  I'm
> > having problems with signals and processes reparenting to init.
> 
> Yeah, I also have these problems. Worked around by bringing down
> the child runsvdir's stuff in stage 3 before bringing down the parent,
> but there are still a few issues.

Would you mind to tell us which ones?

Thanks, Gerrit.


  reply	other threads:[~2004-09-19 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 19:13 Jared Rhine
2004-09-17  2:45 ` mike
2004-09-19 20:02   ` Gerrit Pape [this message]
2004-09-19 20:00 ` 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=20040919200236.28026.qmail@32044832572666.315fe32.mid.smarden.org \
    --to=pape@smarden.org \
    --cc=jared@wordzoo.com \
    /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).