I see the same problem here on my machine. The problem is dhcpd depends on a configured interface to listen on, but the interfaces are handled by the network-manager which is started after dhcpd in the standard setup. Even if I put dhcpd after network-manager in the startup scripts, it takes so long to configure the interfaces that dhcpd is still too fast. I do not know how to only start dhcpd after the interfaces are up. Is there a possibility in network-manager to start up services after interfaces are configured?
-- dhcp3 fails to start during boot-time but starts seamlessly invoking the init-script manually https://bugs.launchpad.net/bugs/61903 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
