From: Paul Sopka <psopka@sopka.ch>
To: supervision@list.skarnet.org,
Laurent Bercot <ska-supervision@skarnet.org>
Subject: Re: Have s6-svscan send SIGTERM to one logger
Date: Mon, 2 Dec 2024 22:05:47 +0100 [thread overview]
Message-ID: <66b93398-3f98-4b6c-b3f2-d91054e727fe@sopka.ch> (raw)
In-Reply-To: <eme1859f9d-a57a-420e-945b-bfd5100e97e0@168760cf.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 963 bytes --]
> 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.
This is what I did before, but in an effort to make the
"sub-supervision-tree"
independent of whatever init-system/service manager is used for the main
tree,
I tried what I described.
Since there is no elegant solution to this,
I will resort to do as you suggest.
A second application for this fifo trick is to have a supervision tree
launched as the child of a graphical session, e.g. a wayland compositor,
to start things like a notification daemon or wallpaper software,
requiring the wayland compositor (and e.g. ${WAYLAND_DISPLAY}) to be set up.
For this application, ist what I proposed the "least bad solution"?
Thank you and have a nice evening
Paul
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-12-02 21:05 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
2024-12-02 21:05 ` Paul Sopka [this message]
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=66b93398-3f98-4b6c-b3f2-d91054e727fe@sopka.ch \
--to=psopka@sopka.ch \
--cc=ska-supervision@skarnet.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).