> You can set the PATH right in the crontab.
Yes, but people don't. I've had to debug other's crontabs many times over the last umpteen years.
But how is that different with systemd timers?
Two environments that set the PATH differently won't have the same value set, either way.
Is this about "yes, but cron doesn't let me trigger through its environment, and systemd timers do"?
But how is that different with systemd timers?
Two environments that set the PATH differently won't have the same value set, either way.
Is this about "yes, but cron doesn't let me trigger through its environment, and systemd timers do"?