3 ms·
That's a really interesting idea that wasn't on my radar. We make extensive use of cron, including fairly complicated job wrappers to do things like provide st
by linsomniac 5y ago
That's a really interesting idea that wasn't on my radar. We make extensive use of cron, including fairly complicated job wrappers to do things like provide status to our monitoring system and prevent running the same job multiple times in parallel. I like to break these out into actual shell scripts if it gets too complicated, but some of these things might be simplified through using systemd units and timers. Plus we could gain some additional functionality, like chaining jobs, which we currently do with "This job shouldn't run more than X minutes, so schedule the follow on job +X minutes from the last one". Plus, do I understand you can schedule jobs on the second?!? :-)
- x0 5y agoLike many things in systemd, timers are a bit complex, I always find myself opening 2-3 manpages at once when doing one. But when you get them set up, it's just a much better system. I still use cron for basic one-liners, but that's it.
- aprdm 5y agoSystems timers do not allow jobs to overlap which is a nice feature vs wrapping a cron on flock