Hello, Le 21/02/2017 à 12:31, Scott Leggett a écrit : > Hi Louis, > > On Wed, 15 Feb 2017 14:34:58 +0100 Louis Bouchard > <louis.bouch...@canonical.com> wrote: >> Hello, >> >> I may be wrong, but this clearly shows that the Unattended Upgrades Shutdown >> unit starts once the target Network is being brought down : > > I don't think the replacement unit I proposed was installed correctly on > your system. Could you double check? > >> Pinging google for 4 seconds is not sufficient, the Unattended upgrade >> shutdown >> can run for saveral minutes before completing. > > This is the express purpose of network.target. Here's the relevant > snippet from `man systemd.special`: > > network.target > This unit is supposed to indicate when network functionality is > available, but it is only very weakly defined what that is supposed > to mean, with one exception: at shutdown, a unit that is ordered > after network.target will be stopped before the network — to > whatever level it might be set up then — is shut down. It is hence > useful when writing service files that require network access on > shutdown, which should order themselves after this target, but not > pull it in. Also see Running Services After the Network is up[1] for > more information. Also see network-online.target described above. >
The unit was correctly installed but another issue made it show as an incorrect behavior. It now tests correctly and I am preparing an upload to our development release. Thanks Kind regards, ...Louis -- Louis Bouchard Software engineer, Cloud & Sustaining eng. Canonical Ltd Ubuntu developer Debian Maintainer GPG : 429D 7A3B DD05 B6F8 AF63 B9C4 8B3D 867C 823E 7A61
signature.asc
Description: OpenPGP digital signature
