4 ms·
Define a unit and run it individually to troubleshoot vs modifying the crontab for 1 min ahead Logging in journalctl Built in jitter options to spread tasks acr
by cripblip 7y ago
Define a unit and run it individually to troubleshoot vs modifying the crontab for 1 min ahead
Logging in journalctl
Built in jitter options to spread tasks across a window in a large fleet
Ability to use the unit as a dep for other things
Instrumented in systemctl list-timers
Store config in user home dir (I think ) for tasks owned by a user
- simcop2387 7y agoAlso the ability to easily keep the task from running multiple copies at once.
- gorgoiler 7y agoThese aren’t really better, they are just different ways of doing things the old fashioned way. (e.g. put all your logic in one script, test it with “env -“, lock exclusively with flock if you need it, or whatever else you have to hand in your language of choice.)
- cripblip 7y ago:shrug:, yeah the old fashioned way is possible too (I have to support both), systemd just gives a consistent pattern to make common tasks easy.