From: Charles Duffy <Charles_Duffy@messageone.com>
To: supervision@list.skarnet.org
Subject: runit customized control hooks
Date: Tue, 01 Jul 2008 20:38:06 -0500 [thread overview]
Message-ID: <g4em62$va3$1@ger.gmane.org> (raw)
A few notes. These observations were made with runit 1.8.0, but I've
checked the release announcements to ensure that 1.9.0 has no pertinent
changes. It may be that they call for nothing more than clarifications
to the docs.
- "u" control hook exit status 0 does not prevent the associated
service from being started.
- "sv u" on an already-started script does not invoke the u control
hook again; likewise, "sv d" on an already-stopped does not reinvoke the
d hook. For my immediate use case (which is admittedly an oddball), this
is unfortunate behavior (I have hooks which could have behaviors
meaningful in this situation); more significantly, though, I believe it
constitutes ambiguously documented behavior, as the runsv man page does
not specify whether the prior-state checks which are prerequisite to
sending a signal or changing state are also prerequisite to custom
control hook invocation.
reply other threads:[~2008-07-02 1:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='g4em62$va3$1@ger.gmane.org' \
--to=charles_duffy@messageone.com \
--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).