On Thu, 21 Jun 2018 20:47:36 +0200 Michael Biebl wrote: > Am 21.06.2018 um 19:36 schrieb Francesco Poli (wintermute): [...] > > systemd-timesyncd [...] > > used to refuse to start, whenever other NTP clients (such as chrony) > > were used. [...] > > But, as soon as I issue: > > > > # service systemd-timesyncd start > > > > chrony dies and systemd-timesyncd starts. > > If you manually start systemd-timesyncd, then indeed chronyd is stopped
But then, this can happen whenever services are (re-)started, such as at boot time or when "systemctl daemon-reexec" is issued. Depending on the order for the various services, this could result in having to manually restart chrony, just to stop systemd-timesyncd... > > > I thought that systemd-timesyncd should refrain from starting and > > leave chrony alone. > > No, Conflicts work both ways. > > Afaics, everything is working as expected, so closing this bug report. Wait, let me clarify how I see it. Some time ago, I just had to install chrony (and set it up) in order to make it work, without systemd-timesyncd interfering. Now, it seems that I will *also* have to manually issue the following command: # systemctl --now mask systemd-timesyncd before installing and configuring chrony. Is this correct? This looks like a regression. Do you agree? -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpEOOGfAh0dh.pgp
Description: PGP signature
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
