> - Unnecessarily complicated and unfamiliar init script structure.
Unfamiliar, yes. Complicated? You have to be kidding me. systemd "scripts" remove the crud and hacks that the old init system built up over years.
Unfamiliar, yes. Complicated? You have to be kidding me. systemd "scripts" remove the crud and hacks that the old init system built up over years.
Run a cron job on systemd; create two files: one timer unit (about 5-7 lines) and one service unit (about 5-7 lines) that you have to name identically (minus the extension) with the timer unit.
systemd can launch a cron daemon which itself can run cron jobs.
in addition, systemd can also execute timer units periodically. This is functionality that sysv init lacks.
If you select the same cron daemon, the configuration of cron jobs may be performed in an identical manner, regardless of which init system has launched that daemon.
Are you complaining that the optional systemd timer functionality is difficult to use and that you would prefer to run cron jobs via a dedicated cron daemon? That may be a valid criticism, but I am a systemd user and I have never tried this functionality, so I cannot comment on it. I personally continue to use a cron daemon since this is what I am familiar with.
Do you have a philosophical objection to the init system providing such capabilities? Maybe there is a valid reason to have such an objection, but I do not hold this perspective personally.
Regardless, your comparison here is not valid, since you are comparing the process of configuring optional functionality in systemd (which has no equivalent with sysv) to the process of configuring a cron daemon (which you could just as easily be using with either init system).
https://wiki.archlinux.org/index.php/Network_configuration#P...
You present this as if this makes sysvinit somehow lesser because of it lacks the ability to execute timer units. Sysvinit doesn't have that because that capability is completely unrelated to what sysvinit does. Although one could argue that the system as a whole provides that functionality through cron anyway, so there'd be no need to have sysvinit do it.