Control: close -1 On Sun, 22 Sep 2019 15:39:24 +0200 Michael Biebl <[email protected]> wrote: > Am 22.09.19 um 14:08 schrieb Marc Haber: > > On Sat, Sep 21, 2019 at 05:05:10PM +0200, Michael Biebl wrote: > >>> 58 systemd-time-wait-sync.service start running > >> > >> Hm, this service is not enabled by default and I'm guessing it prevents > >> time-sync.target to be reached, blocking all subsequent services. > >> > >> Have you enabled this service manually? > > > > Not that I am aware of. The link dates back to August 8, the machine > > has been updated and rebooted multiple times since then without > > problems, there were no significant changes to the machine. The system > > logs don't show the service being enabled manually (auth.log should have > > a sudo entry if I did that manally, I never work in a root shell but > > prefix every root command with its own sudo call for exactly this > > reason). > > > All I can say for sure is that the Debian systemd package never > explicitly enabled this service. Looking at codesearch.debian.net I > don't find any other package referencing that service either. > > 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).
Given this was never enabled, and there are no other configuration or patches, and it is tracked upstream, closing. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
