*** This bug is a duplicate of bug 847782 ***
https://bugs.launchpad.net/bugs/847782
Introducing any kind of script to /etc/network/if-up.d/ that exits with
error for eth0 (or in any case static interfaces?) will cause this
script to fail, ie. introduce the 120 sec boot delay.
I think it is really bad behavior to consider static network up a must
for booting. Static services would already have executed (or tried to
execute) from /etc/network/if-up.d/ and they failed if they came after
the failing script.
In other words run-parts is executed with the fail-on-fail option (the
default).
Should network fail really cause a boot delay?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/845914
Title:
Failsafe boot delay causes a real delay on every boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/845914/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
