On January 8, 2020 7:57:51 PM UTC, Noah Meyerhans <no...@debian.org> wrote: > >The big drawback of systemd timers, IMO, is that a nonzero exit code >doesn't generate email by default the way cron does. At smaller sites, >anyway, this is a perfectly sensible way of being notified of problems >with the job. That's correct, they log the failure to the journal and/or syslog, but do not email. You can use OnFailure to send an email... not sure if there is a way to do that by default. Also, don't think anyone has mentioned it, but "systemctl list-timers" is a nice advantage of timers, too. And it can actually take into account the randomized start delay, something no cron-equivalent could do.
- Re: migration from cron.daily to systemd timer... Daniel Leidert
- Re: migration from cron.daily to systemd t... Noah Meyerhans
- Re: migration from cron.daily to syste... Daniel Leidert
- Re: migration from cron.daily to systemd t... Russ Allbery
- Re: migration from cron.daily to syste... Michael Stone
- Re: migration from cron.daily to ... Russ Allbery
- Re: migration from cron.daily to ... Noah Meyerhans
- Re: migration from cron.daily to ... Stephan Seitz
- Re: migration from cron.daily to ... Russ Allbery
- Re: migration from cron.daily to ... Noah Meyerhans
- Re: migration from cron.daily to ... Anthony DeRobertis
- Re: migration from cron.daily to ... Richard Laager
- Re: migration from cron.daily to ... Paul Wise
- Re: migration from cron.daily to ... Michael Stone
- Re: migration from cron.daily to ... Russ Allbery
- Re: migration from cron.daily to ... Michael Stone
- Re: migration from cron.daily to ... Michael Biebl
- Re: migration from cron.daily to systemd timers Philip Hands
- Re: migration from cron.daily to systemd timers Daniel Leidert
- Re: migration from cron.daily to systemd timer... Philipp Kern
- Re: migration from cron.daily to systemd t... Daniel Leidert