> 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
Received on Mon Dec 02 2024 - 22:05:47 CET