| > What do you mean by "you would expect" I mean it should include things that are usually on the path, like /usr/local/bin. And for the root user it should include sbin. I don't really expect /opt/foo/bin to be there, but if you want to have it available by default everywhere then you can just add it to systemd once, rather than having to remember to add it to crontab as well. > Or on the line, right? Oh you're right. I forgot cron evaluates the command with the shell (which has its own set of issues...) > This is incorrect. You can definitely use $HOME in user crontabs. You can in the command itself, because that is evaluated by a shell, but not when setting an environment variable. From the Ubuntu crontab(5) manpage: > The value string is not parsed for environmental substitutions or replacement of variables or tilde(~) expansion Maybe it depends on the cron implementation though. The cronie documentation doesn't say either way. |
So changing the default PATH for cron requires a green field rewrite? You would expect /usr/local/bin. cron doesn't include it. It seems like a disagreement on default settings. I would agree with you about what the default should be, but I don't understand how this has anything to do with cron either as code or architecture.
This seems a bit like /sbin being missing in the default PATH for the root user's regular shell being a reason to rewrite bash to systemd shell.