I have been facing a similar problem, though with the scripts from another package "firestarter". But, until I came across this page, I had no idea why I was facing this problem. I figure there might be other scripts too that exit with a non-zero code. Couldn't the logging part be implemented in ifupdown itself, and it be allowed to move on, without having to stop. In my situation, I thought I was stuck, and when I rebooted into recovery, I had no internet. Only after manually enabling, setting up my Ethernet could I resume boot. But it might not be as simple to other users.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/916890 Title: "Waiting for network configuration" on every boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/916890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
