Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the manpage is now wrong. It says:
> Several environment variables are set up automatically by the cron(8) daemon. > […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be overridden > by settings in the crontab […] and also > On the Debian GNU/Linux system, cron supports the pam_env module, and loads > the environment specified by /etc/environment and /etc/security/pam_env.conf. > It also reads locale information from /etc/default/locale. However, the PAM > settings do NOT override the settings described above nor any settings in the > crontab file itself. Note in particular that if you want a PATH other than > "/usr/bin:/bin", you will need to set it in the crontab file. These should be fixed I think. There might be other spots that I didn't notice yet too. Secondly, as there are now tasks for stable releases, I think the SRU team needs to be made aware of the implications of SRUing this change. It means that the default PATH (if not overridden) will be different after applying the update. There's a chance that users will then have different copies of programs found resulting in their cron scripts potentially experiencing behaviour changes. The benefits of consistency may outweigh the risks/drawbacks of this behaviour change, but I think it should be considered carefully when SRUing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
