networkd can be configured with interfaces that are RequiredForOnline=no
which will prevent boot delays; ultimately it's up to the system
administrator to decide which interfaces are 'required' at boot time and
configure them appropriately
** Changed in: systemd (Ubuntu)
Status: New => Inva
Edit: Now at the next boot the maximum time the job shows to wait was 5
minutes and 3 seconds so the time seems to get a bit generated for some
reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964
The boot is still delayed even with systemd 232-21ubuntu2 on Ubuntu
17.04 dev if something causes the network not to get up (for example as
it is happening here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681190 ). Also
the time the job does now wait (as shown) seems to be 5 minutes an
I think the default behaviour should be that network problems shouldn't
block login. The exception may be a dedicated workstation with remotely
mounted home directories, where you may want it to block forever. The
current compromise of waiting 120s isn't correct for either situation.
There's also
This bug is something similar:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1094593.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964775
Title:
Boot is delayed due to missing static netwo
So is this:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/940485
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964775
Title:
Boot is delayed due to missing static network interface
To mana
As I migrated from Lucid to Precise there was quite a bump when I realized that
following lines:
auto eth0
auto eth1
would unsuspectingly have quite an impact on boot time if one of cables is
currently unplugged.
Users who use mobile phones with auto/static configurations also have
same problem
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964775
Title:
Boo
I wonder if we could emit failsafe-boot on 'stopped networking'. At that
point, udev has done its thing, and ifup -a has tried to bring up any
network interfaces that exist. So in theory, there's nothing left to
wait for even if there are auto interfaces not up yet.
--
You received this bug notif
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964775
Title:
Boot is delayed due to missing static network interface
To manage noti
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964775
Title:
Boot is delayed due to missing static network interface
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
11 matches
Mail list logo
