Since your s6-svscan doesn't run as pid 1, you don't need a finish or a
crash script. Not creating the .s6-svscan directory at all is good: the
default behaviour is suitable for running s6-svscan as a normal service.
The answer to the rest of your questions implies policy decisions. In
other words, what do you want the package to do, exactly, and how do you
want it to interact with other services that you want to run under s6?
- Do you want to start an empty supervision tree at boot, and then
have the service manager (probably systemd, here) populate it with
various
symlinks to service directories as it brings services up?
- Do you want to start a pre-populated supervision tree that survives
across reboots, and have packages install their services there and not
be
handled by the service manager at all?
- Do you want another behaviour?
If you're going to make a package, you first need to think about
exactly
what it is you're trying to accomplish. In accurate, painful technical
detail.
--
Laurent
Received on Wed Apr 10 2024 - 11:56:04 CEST