Re:GNU Mcron
by tannhaeuser on Saturday May 05, 2018 @06:38PM
(#17004262)
Systemd doesn't "solve" these problems so much as it puts them into a Windows-y monolith that you then have to understand in its entirety, and have to update all the time, forcing you to startup/shutdown services managed by it. Given its accumulated complexity, systemd isn't viable for HA systems.
> systemd isn't viable for HA systems
You mean, besides all the highly-available systems on which it currently runs? Since it's already part of the two most-used distributions in the world, it's fair to say that it's gotten sufficient exercise such that all of the serious kinks have been worked out by now.
Also, I'm not sure what you mean by having to "update all the time." Sure, systemd gets occasional security/bugfix patches, but so did sysvinit. And like sysvinit, systemd is hot-reloadable, so it's never been a problem in practice.
Right, but cron works everywhere. Also, I can’t say i’ve ever had the thought “you know what cron needs? A steep learning curve and dependency management system.” That’s nuts. Cron isn’t going anywhere anytime soon.
That wasn't the question. The question was, "why should I use systemd?" not "why shouldn't I use cron?"
As for the timer functionality in systemd, the configuration language is, IMO, far easier to understand. It doesn't get any easier than:
[Timer]
OnCalendar=weekly
or: [Timer]
OnStartupSec=0
OnActiveSec=1hSure. But your pitch is incredibly unrealistic for actually convincing anyone systems is obsoleting cron (except for linux distro specific packages, i’m sure).
But seriously though, it solves a lot of problems around dependency and device management, error handling, logging, timer management, and so forth. To be sure, it has a steep learning curve, but I've found the effort invested to be well worth it.