Timers log by default, handle missed runs and can be tested in isolation. Cron is still fine for some jobs.

Cron has run scheduled jobs for decades and it still does the job. systemd timers do the same thing with a few extra properties that matter once a job becomes important.

What timers add

  • Output goes to the journal without extra redirection.
  • A job that was missed while the machine was off can run at the next boot.
  • You can start the same unit by hand to test it, with the same environment.

What they cost

Two files instead of one line, and a slightly longer path to understanding for people who know only cron. For a throwaway job that is not worth it.

A rule of thumb

Keep cron for simple personal jobs. Use timers for anything that other people depend on, that needs logs, or that must survive a reboot without anyone noticing.

D. Okafor

Staff writer (sample byline). Sample author used while the editorial team is being set up. Replace with the real byline.