[bravetraveler]

Yep. Time honored tradition, every cron is edited at least twice. Once to put it there, again to fix PATH.

Everyone who does this enough knows it, everyone else [hopefully] rediscovers. Honest to goodness decades-long cargo culture.

I prefer not having this problem, using "systemd timers" instead. The job and any forked work have a reasonable default path, and observability is worlds better.

Did the last run succeed? When is the next? One command with timers, a guess with cron.

[sgarland]

Literally the only issue I’ve had with cron was a bug [0] for an absurd edge case that I found and fixed.

[0]: https://bugs-devel.debian.org/1019716

[bravetraveler]

Congratulations, myself and several dozens of people I know/mentor have repeated the history I mentioned