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

[Francesco Poli]

Control: reopen -1
Control: retitle -1 systemd: systemd-timesyncd should not run, when chronyd is running


On Fri, 22 Jun 2018 23:46:57 +0200 Francesco Poli wrote:

[...]
> I'll try to keep an eye on the two daemons, to find out which one is
> running and whether something unexpected happens.

Well, something weird is indeed happening.

At each reboot, both daemons (chrony and systemd-timesyncd) are running
simultaneously!
Please take a look at the attached transcripts.


I have to manually stop systemd-timesyncd with

  # service systemd-timesyncd stop

after each boot.
I am again pondering whether I should mask systemd-timesyncd with

  # systemctl --now mask systemd-timesyncd

I hope this won't be needed...


-- 
 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
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: timesyncd1.txt
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180723/0a374e43/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: timesyncd2.txt
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180723/0a374e43/attachment-0003.txt>
-------------- 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/20180723/0a374e43/attachment-0001.sig>