supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Lasse Kliemann <lasse-list-supervision-2007@plastictree.net>
To: supervision@list.skarnet.org
Subject: Re: runsvdir under runsv
Date: Thu, 11 Oct 2007 18:06:39 +0200	[thread overview]
Message-ID: <20071011160639.GK2058@enterprise.starfleet> (raw)
In-Reply-To: <20071011125048.20432.qmail@f42c8ad0f3482a.315fe32.mid.smarden.org>

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

* Gerrit Pape writes:
> On Wed, Oct 10, 2007 at 11:47:12PM +0200, Lasse Kliemann wrote:
> > Well, one could place
> > 
> >    sv x ./service/*
> > 
> > in /service/sub/finish.
> 
> That's what I'd suggest, anything wrong with it?

Maybe it has got a drawback compared to the solution of sending a HUP to the 
runsvdir process (acting on /service/sub/service). Assume this process is 
terminate (by TERM, not HUP), and in the meantime until the finish script 
runs, a directory from /service/sub/service is removed. Then the runsv 
process of that directory will not be terminated.

In other words: runsvdir (by its internal list of all PIDs managed) has a 
better chance for terminating all runsv processes in /service/sub/service 
than a shell script acting based on filenames in /service/sub/service only. 

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2007-10-11 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 13:16 Lasse Kliemann
2007-10-10 19:42 ` Joan Picanyol i Puig
2007-10-10 21:47   ` Lasse Kliemann
2007-10-11 12:50     ` Gerrit Pape
2007-10-11 16:06       ` Lasse Kliemann [this message]

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=20071011160639.GK2058@enterprise.starfleet \
    --to=lasse-list-supervision-2007@plastictree.net \
    --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).