* runit customized control hooks
@ 2008-07-02 1:38 Charles Duffy
0 siblings, 0 replies; only message in thread
From: Charles Duffy @ 2008-07-02 1:38 UTC (permalink / raw)
To: supervision
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-07-02 1:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-07-02 1:38 runit customized control hooks Charles Duffy
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).