Le 23/10/2018 à 15:45, Stephan Seitz a écrit :
> On Di, Okt 23, 2018 at 08:16:51 -0400, Hendrik Boom wrote:
>> On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
>>> Make that: "there *was* a command, chkconfig:"
>>>
>>> It's no longer present in Debian stable (stretch) and later. You can
>>> still find it in oldstable (jessie) though.  See
>>>
>>> https://packages.debian.org/search?arch=any&searchon=contents&keywords=chkconfig
>>>
>>>
>>> # Searching in unstable (sid) lists the command for a small subset of
>>> # architectures but a chkconfig package does not seem to exist ...
>> Why would this have been removed?  Is it no longer wanted for systemd
>> users?  Or is there some other, perhaps legitimately technical, reason
>> for its removal?
>
> As far as I know chkconfig was never a Debian tool. I only know it
> from RPM distros. Maybe someone tried to include chkconfig in Debian,
> but gave up later. Or it never really worked.

    I think this is desired only if you want to enable both rc init
scripts and runit scripts on the same system, which, in my opinion is
not a sane configuration. I think they should be made mutually
exclusive. rc init scripts do not monitor the daemons, therefore the
only reason to have both is if you want to have some daemons monitored
(by runit) and some not monitored (launched by an init script). I think
it would be better to find a method for runit to not monitor a daemon.

    For me, runit is apealing because its scripts are simpler. The
system daemons almost never crash therefore I don't see the need to
monitor them. But, since they never crash, it doesn't harm to monitor
them, of course.

        Didier