4 ms·
This week I have just learned that systemd has an alternative scheduler in addition to cron. At this rate systemd will probably become another new OS on top of
by teleforce 5y ago
This week I have just learned that systemd has an alternative scheduler in addition to cron.
At this rate systemd will probably become another new OS on top of Linux similar to Android.
- pmontra 5y agoYesterday I learned that it has its own alternative to NTP: systemd-timesyncd. Quite a big dose of NIH.
- cturner 5y agoSolving integration problems well is often harder than implementing functionality.
- pmontra 5y agoI second that but unfortunately they implemented only the basic functionality. I quote https://unix.stackexchange.com/a/464729 https://unix.stackexchange.com/a/464729 > systemd-timesyncd does no clock discipline: the clock is not trained or compensated, and internal clock drift over time is not reduced. It has rudimentary logic to adjust poll interval but without disciplining the host will end up with uneven time forever as systemd-timesyncd pushes or pulls at whatever interval it thinks the near-term drift requires. It also can't assess the quality of the remote time source. You're unlikely to get accuracy much greater than 100ms. This is sufficient for simple end user devices like laptops, but it could definitely cause problems for distributed systems that want greater time precision.
- 5e92cb50239222b 5y agoYou mean systemd timers? https://wiki.archlinux.org/title/Systemd/Timers https://wiki.archlinux.org/title/Systemd/Timers They were always there, and they work much better than cron in my experience (you're not forced to use cron expressions because it supports things like human-readable time formats; they can randomize startup times, which is useful for backups; they can put additional constraints (like "start only if network is available"); and they can actually be controlled from a single place (systemctl list-timers) instead of cron files that can be spread across multiple configs and directories in /etc/cron*, and pretty much every single user profile). It's a tiny slice of functionality and it makes a lot of sense to keep it in the service manager. Try harder next time.
- totony 5y agoCron has all these features: - single place control: crontab -e - additional constraints: systemctl status && scirpt.sh - randomize startup times: sleep ${RANDOM:0:MAX} && script.sh The nice thing is that it integrates with the existing infrastructure (shell scripts). This means you don't have to add code to cron to add features. I agree with the 10s of files in /etc/cron.daily, etc. But those are there for convenience (you can even remove them from /etc/crontab)
- zeec123 5y agoThere are some cool features in systemd that are not easy to do in cron. Example: I use restic backup. One timer runs every 24h or on the next boot if there where more than 24h since the last backup as this is a laptop. Also it waits some random amount so that not all script run at the same time after boot. If a backup fails (eg remote server down) it retires every 15min, but no more than one hour before I get an Mail with a detailed report. All really easy in systemd. No scripting required.
- totony 5y agoRedhat made the scripting for you. I don't think it's that complicated of a script (although it would be easier with a retry command) sleep $random for i in 1 2 3 4; do backup && exit 0 sleep 15m done logger "backup failed" exit 1 add script to @startup in crontab or whatever they use. You can use another wrapper that only execute it if the backup is newer than now-24h. Backup could even be remote and you could track it by touching a file in /var Yes systemd might be slightly easier, but that's because they put a lot of money into systemd, not because systemd is a better architecture. It's nice that they open sourced it (although it does give them a competitive edge), but we can't act like what used to be there isn't as good. Someone could have packaged utility wrapper scripts in much less time than it did to add those features to systemd, and these wrapper script would be more widely usable (by init scripts, cronjobs, etc)
- zeec123 5y ago