Systemd timer units: two things cron still cant do (opens in new tab)
Every time I see a cron tab I wonder why nobody reached for systemd timers. Cron works fine until it doesnt, and by then youre already in a hole. Here are the two things that always bite us. 1. Your cron PATH is a coin flip Cron runs everything with a stripped down environment. PATH is usually /usr/bin:/bin. So when you write a cron job that calls vault or python3 or anything not in that short list, it silently fails or runs the wrong binary. Systemd services inherit the full environment from...
Read the original article