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

[Michael Biebl]

Am 21.06.2018 um 23:34 schrieb Francesco Poli:
> On Thu, 21 Jun 2018 22:52:37 +0200 Michael Biebl wrote:
> 
> [...]
>> I would check the journal and try to correlate it with other events
>> based on the timestamp
> 
> By looking at the journal timestamps and the root bash history, it
> really seems that chrony was stopped (and timesyncd was started) when I
> issued the commands:
> 
>   # systemctl daemon-reexec
>   # service systemd-logind restart
> 
> I will look more carefully next time, and I will check if/when chrony
> gets stopped.

Fwiw, I'm aware of
https://github.com/systemd/systemd/issues/7104

Your issue, at least how you described it, sounds different though.
If you explicitly start timesyncd, having chronyd stopped is totally
expected.

If you do have an alternative NTP client installed, the Conflicts should
be sufficient. To be sure timesyncd is not started during boot, you can
simply disable it though.


-- 
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/20180622/e50eddd8/attachment-0002.sig>