From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: Runit 1.2.0 - service/control/c not invoked
Date: Thu, 20 Jan 2005 13:33:43 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0501201331010.11392-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20050113190611.6360.qmail@61dc573d6557fd.315fe32.mid.smarden.org>
On Thu, 13 Jan 2005, Gerrit Pape wrote:
> On Thu, Jan 13, 2005 at 11:41:57AM +0100, Vladimir Smelhaus wrote:
> > it seems to me, that service/control/c are not invoked when runsv gets
> > signal from runsvdir. With runsvctrl is it OK.
>
> Yes, the documentation says that if runsv gets a TERM signal it acts as
> if the character x was written to the control pipe. It should run
> control/x in this case. I've some other changes pending, and'll fix it
> with the next version.
The runsvctrl documentation is now a little out of date, as signals may
not be sent to the running "service" (unless the "service" is defined as
the monitoring/controlling runsv program).
[Perhaps someone here with a free half hour could do some wordsmithing and
send a patch to Gerrit.]
---
Charlie
prev parent reply other threads:[~2005-01-20 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 10:41 Vladimir Smelhaus
2005-01-13 19:07 ` Gerrit Pape
2005-01-20 18:33 ` Charlie Brady [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=Pine.LNX.4.44.0501201331010.11392-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).