> It seems to be a systemd problem/feature that startup gets delayed if
a network connection exists but is not responding.
This would most likely be a bug in the definition of other units on the
system, rather than systemd itself. In normal circumstances, if systemd-
networkd-wait-online.service times out (which is the symptom I assume
you are pointing to here) that does not *necessarily* block startup,
because services that are related to e.g. starting the graphical
environment should have no ordering dependency on network-online.target
(or systemd-networkd-wait-online.service itself).
But, something on this system might be configured that way nonetheless.
You can try looking at:
$ systemctl list-dependencies --reverse network-online.target
$ systemctl list-dependencies network-online.target
$ systemctl list-dependencies --reverse systemd-networkd-wait-online.service
to see if anything sticks out. Please share that output.
Or, you can see if it helps to simply:
$ systemctl disable systemd-networkd-wait-online.service
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2120216
Title:
System boot very slow. Login screen delayed by network problems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2120216/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
