file systems are
unmounted. If you add the shutdown.target to that rule, systemd somehow
thinks it should be run just before shutdown which is obviously too
late. I'm not sure that is a systemd bug or a systemd feature, but
either way it doesn't do what we want.
Regards,
Erik
--
Eri
I have narrowed down. This bug was introduced by the fix in #1618900.
That tries to fix the problem of the the unattended-upgrades.service
by letting it depend on network.target and local-fs.target.
However, that doesn't change any of the dependencies, it only makes
the race window larger.
After s
FWIW, the init script /etc/init.d/unattended-upgrades should be
removed from systemd systems (Xenial, Yaketty).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdo
Public bug reported:
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in
I have also tried to let the systemd unit file for this service WantedBy the
umount.target.
According to the systemd documentation that should make it run before the
filesystems
are unmounted, but apparently that doesn't work. systemctl list-dependencies
still shows
that the unattended-upgrade.s
