Am 22.09.19 um 15:39 schrieb Michael Biebl: > Since you are adamant that you haven't enabled the service manually (at > least not explicitly), I wonder if you used something like "systemctl > preset" in the past and it was enabled because of that (afaics > systemd-time-wait-sync.service is not explicitly disabled).
It could be debated whether the default for systemd-time-wait-sync.service should be disabled. Especially since upstream recommends against enabling such a service by default https://github.com/systemd/systemd/issues/5097#issuecomment-276787961 > I guess the rationale for systemd-time-wait-sync.service is the same as > for NetworkManager-wait-online.service or > systemd-networkd-wait-online.service. > The simple fact that those daemons have started does not mean that you > have network access (or your system clock is synchronized). > > You can probably find out more about it at the initial PR > https://github.com/systemd/systemd/pull/8494 Fwiw, I would have found it much more consistent if the service was named systemd-wait-time-sync.service. The current name is just weird imho. -- 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
