So, comparing apples to apples, the apache22 init script in FreeBSD has around 190 lines, and nginx's ~140, including comments and dependencies. The scripts are quite easy to understand and show how to put everything in place.
Still an order of magnitude more complex than systemd.
Description=MaraDNS secure Domain Name Server (DNS) recursive resolver
None of them are useful to me.
Then what are we discussing? Use your old style sysvinit.
Theoretically. In practice, it overrides the way sysvinit works, and you need to explicitly re-enable it.
I don't know again what you mean. The sysvinit init scripts are still working.
it doesn't, as systemd isn't capturing the program's log.
Because it doesn't suppose to do that. The journald is used internally by systemd, and services can opt-in to use it. It's also a situation of damn if you do, damn if you don't do. How many times I red on Slashdot the complain that with systemd you must have binary logs, or that it takes over logging.
In Roundcube for example you can opt-in into syslog logging. http://trac.roundcube.net/tick... The same options should be there to enable journald logging. At least systemd captures sysout and syserr into the journal, so it's not lost. Another huge improvement over sysvinit. How many times I had to start a daemon manually so I can see the errors from syserr.
But again, the MySQL logs are still there in /var/log ? It's not systemd fault if Oracle is not updating MySQL to use journald.