Martin Steigerwald said on Sat, 29 Jul 2023 10:10:11 +0200

>Steve Litt - 29.07.23, 08:50:48 CEST:
>> This isn't much of a problem, because runit and s6 run scripts are
>> trivial to make, and there's documentation for a lot of them.
>>
>> And don't forget, you can use sysvinit as PID1, and then from
>> /etc/inittab run runit or s6 to do the actual daemon startup work.
>
>There is the package runit-services which contains quite some of them
>already.

And if you can't find the run script you want in the package, see
http://smarden.org/runit/runscripts.html .

If you want to use sysvinit as PID1 but use runit to handle all your
daemons, see http://smarden.org/runit/useinit.html#sysv . This is an
excellent option because you can cut services over one by one. Also,
runit doesn't work well with those few daemons that cannot run in the
foreground, so you can use sysvinit init scripts for those few.

For process dependencies, see
http://smarden.org/runit/dependencies.html and
http://smarden.org/pape/djb/daemontools/noinit.html .

SteveT

Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm