Steve Langasek [2015-04-07 14:22 -0000]: > I'm not sure what you mean by this. We absolutely did block on our network > interfaces when using upstart; just with a 2 minute timeout for any > misconfigured interfaces.
Right, but that should only be done by services which depend on network-online.target IMHO, *not* network.target. The former is done by ifup-wait-all-auto.service. I. e. we don't need to block services which merely want network.target on all interfaces to be up. That's at least the intention. Did I misunderstand you? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1425376 Title: Ubuntu Core provides no console login prompt if network is unavailable Status in Snappy Ubuntu: New Status in cloud-init package in Ubuntu: New Status in ifupdown package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Bug description: Ubuntu Core provides no console login prompt if network is unavailable. If I plug ethernet in, it boots to the login prompt fine. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1425376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
