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>
Subject: Re: pid of controlled service (was Re: runit-1.2.0 available)
Date: Fri, 21 Jan 2005 19:35:21 +0000	[thread overview]
Message-ID: <20050121193424.5788.qmail@9205e057e3be69.315fe32.mid.smarden.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0501201324340.11392-100000@e-smith.charlieb.ott.istop.com>

On Thu, Jan 20, 2005 at 01:30:22PM -0500, Charlie Brady wrote:
> On Sat, 18 Dec 2004, Gerrit Pape wrote:
> > With this version the runsv program makes controlling the service
> > through commands normally sent by runsvctrl configurable; arbitrary
> > actions through external programs can optionally be specified, and
> > signalling of the service disabled if desired.  See the man page[0]
> > for details.
> 
> Looks like it could be a very useful feature.
> 
> I think it could be more useful if runsv would set an environment variable 
> so that the external programs don't need to parse anything if they wish to 
> send signals to, or otherwise query the status of, the controlled program.

I'm not sure that's a good idea.  The pid may change while the external
program is running, better let the runsv program send the signals to the
service.  And if the program really needs the pid, it can get it from
./supervise/pid.

Regards, Gerrit.


  reply	other threads:[~2005-01-21 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-18 19:59 runit-1.2.0 available Gerrit Pape
2005-01-16 12:41 ` runit-1.2.1 available Gerrit Pape
2005-04-09 12:56   ` runit-1.2.2 available Gerrit Pape
2005-04-18 17:40     ` runit-1.2.3 available Gerrit Pape
2005-04-19 10:58       ` Uffe Jakobsen
2005-01-20 18:30 ` pid of controlled service (was Re: runit-1.2.0 available) Charlie Brady
2005-01-21 19:35   ` Gerrit Pape [this message]
2005-01-21 21:01     ` Charlie Brady
2005-01-21 21:47       ` Gerrit Pape
2005-01-21 22:31         ` Charlie Brady

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=20050121193424.5788.qmail@9205e057e3be69.315fe32.mid.smarden.org \
    --to=pape@smarden.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).