On Tue, 24 Jul 2018 22:02:11 +0200 Michael Biebl <[email protected]> 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?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
