As another proposed workaround, I have found that editing /etc/init/rc- sysinit.conf to change the line:
start on filesystem and net-device-up IFACE=lo to: start on filesystem and net-device-up IFACE=br0 also appears to produce the desired result by delaying running of legacy /etc/init.d scripts until after the bridge interface comes up. I am not sure if this will have any other undesirable effects and clearly it would not work on a system without a bridge configured. The best solution still has to be to migrate dhcp3-server to upstart but I hope this helps someone else out in the interim. -- dhcp3-server launches before upstart brings all interface, thus failing to start https://bugs.launchpad.net/bugs/580319 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs