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 the issue of server processes which shouldn't be started until the network is up, and this seems to be one of the motivations for the change to a 120s timeout. Is it a matter of chaining the upstart dependencies differently? Networking problems may need to block certain server processes but not block logging in. It should be easy to alternatively configure the system (presumably by changing one of the upstart files) so that network problems do block login. -- 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/+source/upstart/+bug/964775/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
