Cron & Task Scheduling (Cron/Systemd Timers/At)

Quit guessing if your cron job actually fired

🧩 The Challenge

You stare at a log file wondering if that maintenance script ran or if the crond daemon just gave up on life. It’s frustrating as hell when you have to wait an entire hour just to verify a syntax fix.

💡 The Fix

Use systemd-run to launch your cron command as an ad-hoc transient service. It lets you monitor the process lifecycle and grab the output in real-time without modifying your actual crontab.

systemd-run --user --scope --collect --property=MemoryLimit=500M /path/to/your/script.sh

⚙️ Why It Works

This forces your script to run under the systemd unit manager, meaning you can pull logs directly from journalctl -n 20 without digging through /var/log/syslog or waiting for an email that might not even send.

🚀 Pro-Tip: Stick –wait on that command if you want the shell to block until the task finishes.

Linux Tips & Tricks | © ngelinux.com | 9/6/2026