Triggering regular tasks with Systemd


Compared to good old Cron, the timers from Systemd offer a number of benefits. Systemd is now included with most distributions. The actions can also be started independently of the timer, executed in a very specific environment, assigned to groups, and made dependent on other units.

However, as the simple example from Listing 2 shows, the configuration overhead is significantly higher for Systemd timers. A short line is all it takes with Cron, but with Systemd, you first have to write a complete timer unit. Furthermore, unlike Cron, Systemd cannot send you an email in case of an error and thus draw attention to problems. Systemd timers should therefore not replace Cron, at least not in the near future, but merely supplement it.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy Linux Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Systemd Flatpak Updates

    You can automate Flatpak updates without a package manager using systemd's services and timers.

  • Systemd GUIs

    Graphical frontends make it easier to take full advantage of the Systemd process manager. We examine some leading tools for the KDE environment.

  • Systemd Units

    Systemd units use files to control resources that Systemd manages.

  • Command Line: Systemd

    Wondering what all the fuss is about systemd? We explain the basic concepts and capabilities of the new system management suite – coming soon to a distro near you.

  • Tutorials – Systemd

    Take control of the services running on your Linux machine

comments powered by Disqus
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters

Support Our Work

Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

Learn More