supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jan-willem De Bleser <jw@thescrapyard.org>
To: supervision@list.skarnet.org
Subject: s6-svscan shutdown notification
Date: Wed, 23 Feb 2022 17:27:19 -0800	[thread overview]
Message-ID: <CAHgrPWKqBDgkC1uPPZimpuZAJtaR18fMbc6-HJDOrnf7y1huEg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

Hi,

What's the cleanest way to wait on s6-svscan to shut down after issuing of
a SIGTERM (say s6 via-svscanctl -t)?

I'm using s6 to manage daemons in FreeBSD jails, and am trying to work out
the cleanest way to shut things down. I want to use the built-in 'jail'
command for this since it takes care of host operations like unmounting the
jail filesystems and recovering/freeing network interfaces, but in and of
itself it just issues a SIGKILL inside the jail. It can optionally run a
shutdown script, say one that calls "s6-svscanctl -t", but I need some way
to delay the ending of that script until the supervision tree has actually
shut down: some of the managed processes will need to flush data to disk.

Looking at the documentation, my only option appears to be to check if the
return code of s6-svscanctl is 100, or maybe to monitor for the existence
of .s6-svscan/control (not sure if it's removed on exit). Are there any
other ways to monitor s6-svscan?

Is the communication protocol between s6-svscanctl and s6-svscan via
.s6-svscan/control documented anywhere? These jails are service jails with
no shells installed, so if I have to check for a return code of exactly 100
then I'll have to write a specific tool for that, at which point it may be
better for me to write a 'scanwait' tool of some sort that just checks for
existence.

Cheers,
Jw

             reply	other threads:[~2022-02-24  1:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  1:27 Jan-willem De Bleser [this message]
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

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=CAHgrPWKqBDgkC1uPPZimpuZAJtaR18fMbc6-HJDOrnf7y1huEg@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).