On Wed, 13 Jul 2022 18:17:51 +0200 Andras Korn <[email protected]> wrote: > On Mon, Jul 11, 2022 at 10:47:26AM +0300, Martin-Éric Racine wrote: > > > On Thu, 6 Jan 2022 18:38:47 +0100 Michael Biebl <[email protected]> wrote: > > > On 06.01.22 17:26, Andras Korn wrote: > > > > Package: systemd-timesyncd > > > > Version: 249.7-1 > > > > Severity: normal > > > > Tags: upstream > > > > > > > > Hi, > > > > > > > > I noticed that it took a while for the network to become available > > > > after my > > > > laptop wakes up from suspend. > > > > > > > > I traced the problem to systemd-timesyncd. > > > > > > > > I use dhcpcd5, which ships /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf, > > which > > > > contains the line "systemctl try-restart systemd-timesyncd.service || > > > > :". > > > > > > That file is not shipped by systemd. Why does it restart timesyncd? > > > Why does it so blockingly? Why does it restart timesyncd when the > > > network is still down? > > > > This is dhcpcd's attempt at adding the NTP servers received via DHCP > > options to > > timesyncd's configuration and restarting timesyncd to use them. This should > > only happen once the network has been raised, though, since this is an exit > > hook. > > Is there any particular reason you can't invoke systemctl with --no-block > here?
Good point. Added in Debian Git. Please note that I will be dropping Debian's own deprecated NTP hooks when the next upstream is released, since upstream now includes hooks for timesyncd, in addition to its existing hooks for NTP, OpenNTP and Chrony. Martin-Éric
