Public bug reported:
ntp-systemd-netif.path contains the following:
[Install]
WantedBy=network-pre.target
However, network-pre.target is a passive systemd target. It is used
only for ordering, and is not guaranteed to be pulled in unless
something else calls for it explicitly.
On a host where nothing pulls in network-pre.target, the ntp-systemd-netif path
monitoring never gets started, and so changes in
/run/systemd/netif/leases never trigger the dhclient exit hooks for ntp.
Instead, the systemd unit that starts the path monitoring should be
configured with something like:
[Unit]
Wants=network-pre.target
Before=network-pre.target
[Install]
WantedBy=network.target
** Affects: ntp (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
ntp-systemd-netif.path contains the following:
[Install]
WantedBy=network-pre.target
+ However, network-pre.target is a passive systemd target. It is used
+ only for ordering, and is not guaranteed to be pulled in unless
+ something else calls for it explicitly.
- However, network-pre.target is a passive systemd target. It is used only for
ordering, and is not guaranteed to be pulled in unless something else calls for
it explicitly.
-
- On a host where nothing pulls in network-pre.target, the ntp-systemd-
- netif path monitoring never gets started, and so changes in
+ On a host where nothing pulls in network-pre.target, the ntp-systemd-netif
path monitoring never gets started, and so changes in
/run/systemd/netif/leases never trigger the dhclient exit hooks for ntp.
Instead, the systemd unit that starts the path monitoring should be
configured with something like:
[Unit]
Wants=network-pre.target
Before=network-pre.target
[Install]
WantedBy=network.target
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1888318
Title:
dhclient exit hooks aren't guaranteed to run
Status in ntp package in Ubuntu:
New
Bug description:
ntp-systemd-netif.path contains the following:
[Install]
WantedBy=network-pre.target
However, network-pre.target is a passive systemd target. It is used
only for ordering, and is not guaranteed to be pulled in unless
something else calls for it explicitly.
On a host where nothing pulls in network-pre.target, the ntp-systemd-netif
path monitoring never gets started, and so changes in
/run/systemd/netif/leases never trigger the dhclient exit hooks for ntp.
Instead, the systemd unit that starts the path monitoring should be
configured with something like:
[Unit]
Wants=network-pre.target
Before=network-pre.target
[Install]
WantedBy=network.target
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1888318/+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
