Yurii: can you clarify how that broke unattended upgrades?
I also don't see how a cron script might get different PATH values from one day to the other.
I just had another instance of this bug on a third Ubuntu 14.04 LTS server (this one a physical machine, not a VPS) where unattended-upgrades worked fine before. And on that machine
Yurii: can you clarify how that broke unattended upgrades?
I also don't see how a cron script might get different PATH values from one day to the other.
I just had another instance of this bug on a third Ubuntu 14.04 LTS server (this one a physical machine, not a VPS) where unattended-upgrades worked fine before. And on that machine
# cat /proc/$(pidof cron)/environ | tr '\0' '\n' | grep PATH /usr/local/ sbin:/usr/ local/bin: /usr/bin: /usr/sbin: /sbin:/ bin
PATH=
looks fine to me.