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

[Michael Biebl]

On Tue, 24 Jul 2018 22:02:11 +0200 Michael Biebl <biebl at debian.org> wrote:
> Am 24.07.2018 um 21:33 schrieb Francesco Poli:
> > On Tue, 24 Jul 2018 01:46:51 +0200 Michael Biebl wrote:
> > 
> >> Am 23.07.2018 um 19:53 schrieb Francesco Poli:
> > [...]
> >>> I am again pondering whether I should mask systemd-timesyncd with
> >>>
> >>>   # systemctl --now mask systemd-timesyncd
> >>
> >> systemctl disable  systemd-timesyncd should be sufficient
> > 
> > OK, I disabled systemd-timesyncd: I hope this will work around the bug.
> 
> It most certainly will make sure that timesyncd is not started during boot.
> 
> > However, do you agree that the Conflicts is not working properly?
> 
> Well, see https://github.com/systemd/systemd/issues/7104

Felipe, Martin, what's your take on this, see
https://github.com/systemd/systemd/issues/7104#issuecomment-453783756

Atm, it seems, Conflicts= are not working reliably. So enabling
systemd-timesyncd.service by default and make alternative
implementations declare a Conflicts=systemd-timesyncd.service does not
necessarily result in that alternative actually being started on boot.

Should we re-add the Conditions, i.e. revert
https://salsa.debian.org/systemd-team/systemd/commit/b2ced9989344a22e58cd59427bf1ba6a8bfa9827

(at least for buster).

WDYT?

Michael

-- 
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/20190310/fc102039/attachment.sig>