>I prefer this way. Some packages prefer s6 as their process supervisor,
>some
>packages prefer systemd. With the help of s6 rpm package, other rpm
>packages
>who depend on s6 can install their service in s6’s service directory.
>We just pave
>for the community, the choice is in their hands.
All right. Then, as Guillaume says, you cannot use /run/service as your
scandir, because everything under /run will be wiped at boot time. You
should pick a permanent place, such as (for instance)
/var/lib/s6/service,
and make it your scandir.
All the packages that have services they want s6 to manage will need to
create their own service directories, and symlink them into the scandir.
>Could you tell me how to verify s6-svscan works well as there is
>nothing in log.
Did you start the process? If you did, it's running, and it's working.
If it isn't, it's a bug, either in the way you started it, or in the
code.
Do not runtime-check the result of your policies. If your policy says
that
s6-svscan is started, then you should assume it is working. If it isn't,
it's not something that should be handled at run time, it's something
that
should be handled before anything ships.
--
Laurent
Received on Wed Apr 10 2024 - 16:19:29 CEST