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

[Michael Biebl]

Am 21.06.2018 um 22:07 schrieb Francesco Poli:
> 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.
> 
> Weird!
> 
> 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?

I would check the journal and try to correlate it with other events
based on the timestamp


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180621/546a32b7/attachment-0002.sig>