I too would like to see a solution to this bug. I think a good solution might be to extend NetworkManager so that it can be configured to block until it has brought certain interfaces on-line. So, if you were serving DHCP on eth0 and eth2, you could somehow tell NetworkManager (probably just a checkbox in the GUI interface?) that it must bring those interfaces up when it starts, before forking off. Then, as long as you ran NetworkManager before any other networking daemons on boot, you'd be guaranteed the interfaces your networking daemons need.
Thoughts? -- dhcp3-server is launched before NetworkManager and thus doesn't find interfaces https://bugs.launchpad.net/bugs/392826 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
