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

Stop systemd timers from silently failing on your transient environments

🧩 The Challenge

Setting up a timer to run a script is great until you realize your environment variables are completely missing and the job exits with a status 200 before it even starts. Nobody tells you that systemd timers don’t inherit your login shell’s carefully crafted path or secrets.

💡 The Fix

Use the EnvironmentFile directive inside your service unit to pull in your variables cleanly. It stops those mystery failures where your script can’t find its dependencies or binary paths.

[Service]
Type=oneshot
EnvironmentFile=/etc/default/my-app-env
ExecStart=/usr/local/bin/cleanup-script.sh

⚙️ Why It Works

By explicitly pointing the service to an environment file, you ensure the execution context is identical every single time it fires, regardless of who or what triggered the service. It forces a deterministic state instead of relying on the shaky assumptions of a standard cron environment.

🚀 Pro-Tip: Run systemd-analyze verify on your service files to catch these environment typos before the timer tries to execute them.

Linux Tips & Tricks | © ngelinux.com | 8/30/2026