Systemd Timers vs Cron: Modern Linux Task Automation

Admin

October 3, 2026

5 min read

For decades, cron has been the default standard for scheduling background jobs in Unix-like operating systems. However, modern Linux systems powered by systemd offer a far superior, enterprise-grade alternative: Systemd Timers.

Why Migrate from Cron to Systemd Timers?

Feature	`cron`	`systemd` Timers
Logging	Silent or requires custom file redirection (`>> /var/log/...`)	Centralized in `journalctl` with stdout/stderr capture
Execution Controls	Runs blindly regardless of network/disk state	Can depend on targets (e.g., `network-online.target`)
Resource Limits	Unrestricted by default	Full `cgroups` support (RAM, CPU limits)
Missed Executions	Skipped entirely if system is powered off	A persistent calendar timer runs once after boot if at least one scheduled time was missed
Execution Visibility	Difficult to see next execution time	Clean inspection with `systemctl list-timers`

Architecture: The Service & Timer Pair

A systemd timer requires two paired configuration files located in /etc/systemd/system/ (for system-wide tasks) or ~/.config/systemd/user/ (for unprivileged user tasks):

.service file: Defines what executable or script to run.
.timer file: Defines when and how often the paired service is triggered.

Step 1: Create the Working Script

Create the Working Script

Scripting

Create a configuration-backup script under /usr/local/bin/homelab-backup.sh. It skips example paths that are absent and fails clearly if none exist. This archives configuration only; use an application-aware backup method for databases and other live state.

sudo nano /usr/local/bin/homelab-backup.sh

❯ View Expected Console Output

#!/usr/bin/env bash
set -euo pipefail
umask 077

BACKUP_DIR="/var/backups/homelab"
DATE="$(date +'%Y-%m-%d_%H%M%S')"
mkdir -p "$BACKUP_DIR"

EXPECTED_PATHS=(etc/caddy etc/docker)
SOURCES=()
for path in "${EXPECTED_PATHS[@]}"; do
  [[ -e "/$path" ]] && SOURCES+=("$path")
done
if ((${#SOURCES[@]} == 0)); then
  echo "No configured paths exist; update EXPECTED_PATHS." >&2
  exit 1
fi

echo "[$(date)] Starting configuration backup..."
tar -czf "$BACKUP_DIR/etc-backup-$DATE.tar.gz" -C / -- "${SOURCES[@]}"

# Prune archives older than 14 days.
find "$BACKUP_DIR" -type f -name "*.tar.gz" -mtime +14 -delete
echo "[$(date)] Backup completed successfully."

Ensure the script has executable permissions:

sudo chmod +x /usr/local/bin/homelab-backup.sh

Step 2: Define the Systemd Service Unit

Define the Systemd Service Unit

Systemd Unit

Create /etc/systemd/system/homelab-backup.service. We use Type=oneshot because batch backup tasks run to completion and exit immediately. We also enforce memory and CPU limits:

[Unit]
Description=Automated Homelab Backup Routine
Wants=network-online.target
After=network-online.target

[Service]
Type=oneshot
ExecStart=/usr/local/bin/homelab-backup.sh
User=root
StandardOutput=journal
StandardError=journal
MemoryMax=512M
CPUQuota=50%

Step 3: Define the Systemd Timer Unit

Define the Systemd Timer Unit

Scheduling

Create /etc/systemd/system/homelab-backup.timer. For this calendar timer, Persistent=true triggers one catch-up run after boot if at least one scheduled activation was missed while the system was off. It does not replay every missed interval.

[Unit]
Description=Trigger Homelab Backup Routine Daily

[Timer]
# Run every night at 03:30 AM
OnCalendar=*-*-* 03:30:00
# Randomized delay prevents I/O contention if multiple jobs fire together
RandomizedDelaySec=15m
# Catch up immediately if machine was asleep/offline
Persistent=true

[Install]
WantedBy=timers.target

Step 4: Understanding OnCalendar Schedule Expressions

Verify OnCalendar Schedule Expressions

Validation

Use the built-in systemd-analyze calendar utility to validate your schedule expressions and check when the next execution windows occur:

systemd-analyze calendar "Mon *-*-* 04:00:00"

Quick Reference: Cron vs Systemd Timers

Interval	`cron` Equivalent	`systemd` Timer `OnCalendar` Expression
Every hour	`0 * * * *`	`hourly` or `--* *:00:00`
Daily at midnight	`0 0 * * *`	`daily` or `--* 00:00:00`
Every 15 minutes	`/15 * * *`	`*:0/15`
Every Monday at 4 AM	`0 4 * * 1`	`Mon --* 04:00:00`
Monthly on 1st at 2 AM	`0 2 1 * *`	`--01 02:00:00`

Step 5: Enable, Start & Verify the Timer

Enable, Start & Verify the Timer

Activation

Reload the systemd daemon to pick up the new unit files, then enable and start the timer (not the service directly):

sudo systemctl daemon-reload
sudo systemctl enable --now homelab-backup.timer
systemctl list-timers --all homelab-backup.timer

Step 6: Testing Execution & Journal Auditing

Testing Execution & Journal Auditing

Monitoring

Trigger an on-demand manual execution of the service and inspect the real-time journal logs:

sudo systemctl start homelab-backup.service
sudo journalctl -u homelab-backup.service -n 50 --no-pager