Answer the question
In order to leave comments, you need to log in
What exactly does the long loading of networkd-dispatcher.service mean?
Good afternoon! Still dealing with long system boot times. Previously, it was advised to understand what takes a long time to load: the core or the user space. Here is what the command output systemd-analyze
:
Startup finished in 26.782s (firmware) + 5.687s (loader) + 13.266s (kernel) + 19.411s (userspace) = 1min 5.149s
graphical.target reached after 19.401s in userspace
systemd-analyze critical-chain
resulted in the following:graphical.target @19.401s
└─multi-user.target @19.401s
└─networkd-dispatcher.service @10.290s +9.109s
└─basic.target @10.200s
└─sockets.target @10.200s
└─uuidd.socket @10.200s
└─sysinit.target @10.111s
└─systemd-timesyncd.service @9.977s +133ms
└─systemd-tmpfiles-setup.service @7.842s +2.111s
└─local-fs.target @7.770s
└─boot-efi.mount @7.554s +216ms
└─[email protected]\x2duuid-528C\x2dFBDD.service @6.533s +979ms
└─dev-disk-by\x2duuid-528C\x2dFBDD.device @6.532s
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question