On Sun, 7 Jan 2018 17:53:29 +0100 Vincent Blut <vincent.deb...@free.fr> wrote: > > After reading the bug report again, I notice that I did not ask you to > disable systemd-timesyncd. So could you please run “systemctl disable > systemd-timesyncd” and report chronyd’s status after rebooting?
FWIW, I had the same problem (on an up-to-date Strech machine) and disabling the systemd-timesyncd service seems to have fixed it, chronyd starts up fine now. HTH, -- Mikael
