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

Stop getting hit with stale cron environment variables

🧩 The Challenge

You know the pain when a script runs perfectly fine in your shell but dies a quiet death the moment cron touches it. I’ve spent an entire afternoon debugging PATH issues because the cron daemon doesn’t know about your fancy custom environment settings.

💡 The Fix

Don’t rely on the shell to guess your paths. Just dump the environment directly into your crontab and save yourself the headache.

* * * * * /bin/bash -l -c '/path/to/your/script.sh'

⚙️ Why It Works

Adding the -l flag tells bash to act as a login shell, which forces it to source your profile files just like you were logging in manually. It’s the quickest way to pull in all those exported variables you normally take for granted.

🚀 Pro-Tip: Use absolute paths for everything in your script, even if you think you fixed the environment.

Linux Tips & Tricks | © ngelinux.com | 10/4/2026