6 ms·
> - Unnecessarily complicated and unfamiliar init script structure. Unfamiliar, yes. Complicated? You have to be kidding me. systemd "scripts" remove the crud
by nodata 12y ago
> - 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.
- ultramancool 12y agoSo does FreeBSD's rc system with rc.subr and it's far simpler IMO.
- andmarios 12y agoRun a cron job on sysvinit; add one line to /etc/crontab. 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.
- dnlrn 12y agosysvinit does not handle cron jobs. A cron daemon does. Nothing stops you from using for example cronie with systemd.
- devicenull 12y agoSo then you have two places to look to figure out where a scheduled task is running?
- nodata 12y agoAnd in crond you have three places to look. So?
- JeremyNT 12y agosysv init can launch a cron daemon which itself can run cron jobs. 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).
- ultramancool 12y agoGood comment. I think part of the problem is that some systemd proponents are pushing using it for far too many things. Such as replacing cron or configuring network interfaces. Here's why I was complaining about the network configuration thing on Arch: https://wiki.archlinux.org/index.php/Network_configuration#Persistent_configuration_on_boot_using_systemd https://wiki.archlinux.org/index.php/Network_configuration#P...
- thwarted 12y agoin addition, systemd can also execute timer units periodically. This is functionality that sysv init lacks. 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.
- andmarios 12y agoI have in my mind CoreOS which does not provide a cron daemon nor any way to install one. So using systemd timers is the only way to get cron functionality.
- pessimizer 12y agoAnd replace them with something sprawling, tangled, unauditable and 5x the size.
- feld 12y agoFreeBSD removed the "crud" by standardizing all of the tasks people want to do into rc.subr. As a result you get some pretty clean and easy to understand rc/init scripts except in extreme circumstances.