Re: Probably a necessity
What I do not agree on is on init scripts being simple:
wc -l /etc/init.d/httpd
Well, I don't know which distro you're using, because on my machine :-
[vic@perridge ~]$ wc -l /etc/init.d/httpd
And it's a really simple script. 37 lines in mine are whole-line comments. This is a very simple thing.
wc -l /usr/lib/systemd/system/httpd.service
So you think fewer LoC means simpler? I despair of such attitudes.
But when we add in /etc/sysconfig/httpd - which is where the config bits have gone to from the init file, there's another 38 lines.
But - and here's the rub - what happens when something goes wrong? You've got your minimalist httpd.service, and it just doesn't start the daemon - what do you do? With an init script, you can run each command and see what the hell happens - because that is exactly the context in which the script will usually be run. If your systemd getup fails for any reason, you have some work on your hands.
The rest of the stuff is exactly the same, you are not forced to use anything in Systemd that you do not want to
If that were true, there would be far less aggro. In pont of fact, you now have more and more things in the G/L system that require systemd, even if they're not trying to run daemons. If this were not so, then efforts like devuan would be trivial.
So that is why some of us do not want systemd - and it had nothing to do with its capabilities as a startup system. That much notwithstanding, the "benefits" of systemd you have listed above really don't qualify as such in my world. And whoever wrote your /etc/init.d/httpd seems to have issues...