From: Jan-willem De Bleser <jw@thescrapyard.org>
To: supervision@list.skarnet.org
Subject: Re: s6-svscan shutdown notification
Date: Sat, 26 Feb 2022 08:12:58 -0800 [thread overview]
Message-ID: <CAHgrPWKUuDSTyQS7AcpEzce=m1MsL5YdZYkmz=yzFw1dkHkSEg@mail.gmail.com> (raw)
In-Reply-To: <0cb9bb90-f63e-5dbe-b890-f03803b7c9e4@rlwinm.de>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Fri, Feb 25, 2022 at 8:52 AM Jan Bramkamp <crest@rlwinm.de> wrote:
> I use s6-rc on the FreeBSD jail host as well to manage jails with their
> own supervision trees as long running services making the jail
> supervision tree a subtree of the host supervision tree. I prefer to let
> s6-rc handle state transitions instead of using the more limited state
> management support in the jail utility. I use one service bundle per
> jail containing a oneshot to create/destroy a persistent jail and a long
> run depending on the oneshot using jexec to start the supervision
> subtree inside the jail.
>
I can see the appeal of that, using one-shots to set up the network,
mounts, etc. I don't use s6-rc, but I'll keep it in mind.
However, I realized I've framed the issue incorrectly: I don't care if s6
receives a SIGKILL as long as the supervised processes (including loggers)
have shut down cleanly. I can use elglob/forx/s6-svc -wD to shut everything
down, and just not worry about s6-svscan.
- Jw
prev parent reply other threads:[~2022-02-26 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 1:27 Jan-willem De Bleser
2022-02-24 5:04 ` Laurent Bercot
2022-02-24 5:16 ` Jan-willem De Bleser
2022-02-25 16:52 ` Jan Bramkamp
2022-02-26 16:12 ` Jan-willem De Bleser [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='CAHgrPWKUuDSTyQS7AcpEzce=m1MsL5YdZYkmz=yzFw1dkHkSEg@mail.gmail.com' \
--to=jw@thescrapyard.org \
--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).