Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

Francesco Poli invernomuto at paranoici.org
Thu Jun 21 21:07:30 BST 2018

On Thu, 21 Jun 2018 21:57:29 +0200 Michael Biebl wrote:

> Am 21.06.2018 um 21:16 schrieb Francesco Poli:
> > 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?
> > 
> No, this is not correct.


The fact is that, at some point, I found out that chrony was no longer
running on my box, while systemd-timesyncd was somehow running instead.

I am pretty sure I had *not* manually issued a "service
systemd-timesyncd start" command before that point in time.
I only issued that command afterwards, while investigating the mystery,
and saw that it had the power to stop chrony.

Do you have any idea about what could have happened?

Thanks for your prompt replies and for any additional help you may

 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180621/87c378c7/attachment-0002.sig>

More information about the Pkg-systemd-maintainers mailing list