The Slackware 15.0 ships a daemon supervisor designed exactly to supervise init system's services and Mr. Hameleers has a package of it for Slackware 14.2 - it's name is "daemon"

True, this daemon supervisor was added to Slackware mainly because its unique feature of integration with elogind (added on our request), and usually it's used by us to supervise the PipeWire daemons on user side and to gracefully quit them on user logout, BUT nothing stops you to use it for its original purpose of managing and monitoring init system's services.

Yes, today the Slackware ships a fine daemon supervisor, and it's also perfectly compatible with sysV init and its scripts - it's just a program to execute and control another program or even a script.

And Slackware demonstrated practically that there is no need to change the sysV init system to "supervise services" as you like.

For the sake of illustration, say using dovecot as example, could you show how this would work?

You still have to make changes to actually run those services under daemon.

I don't think anybody here would argue that having choices is somehow a bad thing, at least not in this context.

"Need" is in the eye of the beholder.

I just released a beta version. https://www.linuxquestions.org/quest...em-4175713440/