I would love to know, how you would implement systemd's features without departing significantly from SysV init. Especially systemd's ability to reliably kill a daemon and all it's child processes. This feature alone would make me switch to systemd immediately, since it makes cluster failover much more reliable. File systems can only be unmounted if all processes accessing them are killed. So we need reliable killing to unmount and switch the drbd node to secondary.
I will not for one second miss the whole "oh the daemon could not write it's PID file, but it started anyway and now the init script cannot stop it anymore" mess... Or the init script shows a green "done" but it didn't notice that apache died immediately afterwards.
systemd solves real problems for real users. It does so at the cost of and hour or two of learning how to use it versus the 17 years of experience one needed to get SysV based systems to run reliably.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds