On Mon, Mar 21, 2022 at 05:57:10PM +0100, Michael Biebl wrote:
> Control: reassign dhcpcd5
>
> Am 21.03.22 um 17:39 schrieb Michael Biebl:
> >
> > Am 21.03.22 um 17:36 schrieb Michael Biebl:
> >
> > > Is that a result of /etc/dhcp/dhclient-exit-hooks.d/timesyncd ?
> > >
> > > What happens if you remove that dhclient hook
> >
> >
> > Actually, I think it might be
> > dhcpcd5: /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf
> >
> > which triggers the service restart, i.e. it would be a dhcpcd5 issue.
>
> Reassigning accordingly.
>
> # cat /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf
> # vi: ft=sh
>
> SERVERFILE_IPV4="/run/systemd/timesyncd.conf.d/01-dhcpcd.ipv4.$interface.conf"
> SERVERFILE_IPV6="/run/systemd/timesyncd.conf.d/01-dhcpcd.ipv6.$interface.conf"
>
> reload_config() {
> systemctl try-restart systemd-timesyncd.service || :
> }
Fantastic, thank you! I've confirmed that replacing that line with a
simple `:` stops this behaviour.
