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

Michael Biebl biebl at debian.org
Thu Jun 21 20:56:31 BST 2018

Am 21.06.2018 um 21:16 schrieb Francesco Poli:
> 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.

It should not happen during boot time, as the ConflictedBy service will
not be started.

daemon-reexec does not restart services.

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/7092001b/attachment-0002.sig>

More information about the Pkg-systemd-maintainers mailing list