supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Paul Sopka" <psopka@sopka.ch>,
	"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: Have s6-svscan send SIGTERM to one logger
Date: Mon, 02 Dec 2024 19:37:49 +0000	[thread overview]
Message-ID: <eme1859f9d-a57a-420e-945b-bfd5100e97e0@168760cf.com> (raw)
In-Reply-To: <1a2c16c9-a1af-45f5-82ca-03c8c6b9da2b@sopka.ch>

>I have a logger supervised by the very s6-svscan instance it logs through the fifo trick.
>Now sending SIGTERM to the s6-svscan process won't work, since it waits for the logger forever,
>which in turn waits for s6-svscan to close the fifo.

  There is no good solution to this. s6-svscan, the catch-all logger's
s6-supervise, and the catch-all logger, are codependent. This is why
the construct should only be done once, for the root supervision tree,
and the catch-all logger never needs to be killed. (It logs to a RAM
filesystem so its existence does not prevent any unmounting.)


>Since this is not the main supervision tree, I require the ability to stop this instance of s6-svscan.

  If this is not the main supervision tree, there is no reason for you
to use the fifo trick and have the s6-svscan log to something under
itself.
  Start the inner s6-svscan as a regular service, with a logger that is
supervised by the *outer* supervision tree.

--
  Laurent


  reply	other threads:[~2024-12-02 19:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 17:35 Paul Sopka
2024-12-02 19:37 ` Laurent Bercot [this message]
2024-12-02 21:05   ` Paul Sopka
2024-12-03  0:56     ` Re[2]: " Laurent Bercot

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=eme1859f9d-a57a-420e-945b-bfd5100e97e0@168760cf.com \
    --to=ska-supervision@skarnet.org \
    --cc=psopka@sopka.ch \
    --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).