From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: pid of controlled service (was Re: runit-1.2.0 available)
Date: Fri, 21 Jan 2005 16:01:54 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0501211558530.6361-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20050121193424.5788.qmail@9205e057e3be69.315fe32.mid.smarden.org>
On Fri, 21 Jan 2005, Gerrit Pape wrote:
> > 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.
I don't know how that would be possible if you wanted a custom handler to
do something special and then pass the signal on to the daemon. The custom
handler would have no way of asking the runsv process to deliver the signal,
correct?
> And if the program really needs the pid, it can get it from
> ./supervise/pid.
Ah, yes, I forgot that.
next prev parent reply other threads:[~2005-01-21 21:01 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
2005-01-21 21:01 ` Charlie Brady [this message]
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=Pine.LNX.4.44.0501211558530.6361-100000@e-smith.charlieb.ott.istop.com \
--to=charlieb-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).