32
top 9 comments
sorted by: hot top controversial new old
[-] spicystraw@lemmy.world 2 points 13 hours ago

I like this post! It's an easy, informative read. Nice to see some useful info about systemd for once, instead of simple "systemd bad"

[-] syklemil@discuss.tchncs.de 8 points 1 day ago

post from 2025

systemd is a relatively new utility that provides an array of components for Linux systems.

what


Snideness aside, systemd timers can be pretty neat. They also have some features like being able to specify "Daily" and setting some looseness in when it triggers if you e.g. have a fleet of machines and don't want them all to do something at exactly the same time.

[-] Badabinski@kbin.earth 7 points 1 day ago

To be fair, it is relatively new. Cron will be 50 this year which blows my fucking mind.

[-] BlackEco@lemmy.blackeco.com 4 points 1 day ago

The author fails to mention you can also use timers to do schedules like "every 15 minutes, 5 minutes after the systemd started". Very useful for scheduling automatic updates or backups.

[-] SquiffSquiff@lemmy.world -2 points 1 day ago

How are systemd timers not a solution looking for a problem?

[-] MadhuGururajan@programming.dev 4 points 1 day ago
[-] SquiffSquiff@lemmy.world 2 points 1 day ago

Cron already exists and is established as the solution in this space. It's also used as the model for a lot of other timer services outside the Linux kernel.

[-] MadhuGururajan@programming.dev 1 points 9 hours ago

cron is quite inadequate for condition based scheduling. Instead of million obscure ways to achieve this inside the command that cron executes, systemd timers give us a standard ONE way to do things.

I feel like systemd timers follow unix philosophy better than cron at this day and age.

[-] BlackEco@lemmy.blackeco.com 7 points 1 day ago* (last edited 1 day ago)

Have you read the article? The fourth paragraph lists improvements systemd timers bring over cron:

Cron is easy, very simple and robust mechanism to execute periodic tasks on a *nix server, and is available by default on all popular Linux distributions. However, cron suffers from some issues:

  • If the system is down when the cron needs to run, the cron will be missed

  • There is no built-in status monitoring

  • There are no built-in logs

  • If you want to execute pre/post commands (for example by pinging an external service for success/failure) you have to do it inside the script itself

All of these issues are addressed with systemd services and timers, as the authors explains in details.

this post was submitted on 14 Mar 2025
32 points (92.1% liked)

Linux

6466 readers
695 users here now

A community for everything relating to the GNU/Linux operating system

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS