Comment 27 for bug 916890

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.