From: Charles Duffy <cduffy@spamcop.net>
Subject: Re: runit under sysvinit - coping when runsvdir dies
Date: Thu, 17 Nov 2005 05:13:55 -0600 [thread overview]
Message-ID: <dlholk$9b6$1@sea.gmane.org> (raw)
In-Reply-To: <20051117090319.29817.qmail@f69151e2a0a700.315fe32.mid.smarden.org>
Gerrit Pape wrote:
> If runsvdir receives the HUP signal, it sends a term signal to all runsv
> processes it manages. On the TERM signal, it simply exits, leaving the
> runsv processes alone. Maybe I should switch that, so that TERM signals
> 'by mistake' are handled better. It then would re-init the complete
> system, stopping all services plus supervisors on TERM, and starting
> them up again after being re-spawned through inittab.
In cases where runsvdir is going to be automatically respawned on exit,
this certainly seems to make sense, though you're right inasmuch as
there's potential for side-effects on the system shutdown procedure...
how about having a file's (non)existance be used to control this
behaviour, akin to where runit-init checks for the existance of stopit
before shutting down?
prev parent reply other threads:[~2005-11-17 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 18:03 Charles Duffy
2005-11-16 3:50 ` Charlie Brady
2005-11-17 9:08 ` Gerrit Pape
2005-11-17 11:13 ` Charles Duffy [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='dlholk$9b6$1@sea.gmane.org' \
--to=cduffy@spamcop.net \
/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).