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
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779767

Title:
  Default cron PATH does not include /snap/bin

Status in anacron package in Ubuntu:
  Fix Committed
Status in cron package in Ubuntu:
  Fix Committed
Status in anacron source package in Bionic:
  Confirmed
Status in cron source package in Bionic:
  Confirmed
Status in anacron source package in Focal:
  Confirmed
Status in cron source package in Focal:
  Confirmed
Status in anacron source package in Groovy:
  Confirmed
Status in cron source package in Groovy:
  Confirmed
Status in anacron source package in Hirsute:
  Fix Committed
Status in cron source package in Hirsute:
  Fix Committed

Bug description:
  I recently changed from a .deb install of LXD to a snap, and was
  surprised that one of my crontab scripts stopped working.

  I see that $PATH in a cron script only contains "/usr/bin:/bin",
  whereas my default shell also includes "/snap/bin".

  It seems to me that for the best user experience with snaps,
  "/snap/bin" should be part of the default $PATH in cron.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  2 14:30:06 2018
  InstallationDate: Installed on 2017-12-20 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to