I hit this issue today, on karmic. dhcpd _sometimes_ fails to start on
manually configured interfaces.
IMHO this happens because there is a race between the new
/etc/init/networking.conf from upstart/ifupdown and the old
/etc/rc2.d/S40dhcp3-server. Nothing makes sure that networking is fully
up before the start-scripts for (e.g.) runlevel 2 are started (in former
times, this was of course guaranteed by the sysinit scripts). The
appended patch makes sure that all multi-user runlevel scripts are
executed only after networking (ifup -a) has completed.
I think this bug could also affect other services with only sysvinit-
compatible start scripts.
--
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
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
