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

Stop cron jobs from failing silently because of the environment

🧩 The Challenge

You’ve spent an hour writing a perfect script, only for it to fail the second cron executes it. It’s always the same story: your paths and variables aren’t loaded, so the script dies the moment it tries to call anything outside of /usr/bin.

💡 The Fix

Start sourcing your user profile or explicitly setting your path inside the cron entry itself. It’s a messy little hack, but it saves you from the inevitable “command not found” error when you least expect it.

* * * * * . $HOME/.bash_profile; /usr/local/bin/your_script.sh >> /tmp/cron.log 2>&1

⚙️ Why It Works

Cron runs with a bare-bones environment that ignores your interactive shell configs by design. By forcing a source of your profile before the command, you ensure the script sees exactly what you see when you run it from your terminal.

🚀 Pro-Tip: Use the full absolute path for every single binary in your script; don’t rely on PATH at all if you can help it.

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