I spoke with Keybuk briefly about changing the startup conditions for runlevel 2, and he warned that there may be one unforseen circumstance.
Its possible right now to have a sysvinit script that supports a network interface coming up. Meaning that there may be an interface that will spin while coming up until a sysvinit daemon starts, blocking ifup -a from completing (and therefor delaying 'started networking'). This can happen because we start runlevel 2 as soon as we have a loopback device, so ifup continues beyond that in parallel with sysvinit. So, we may need to review all ifup pre/post scripts to make sure they don't wait on sysvinit scripts, and if they do, change them to fork into the background to do so. We'd also need to document this behavioral change in the release notes so people can test any custom setups before upgrade. On Mon, 2011-03-14 at 23:37 +0000, Dave Walker wrote: > Does this specific issue also relate to isc-dhcp ? > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. https://bugs.launchpad.net/bugs/580319 Title: dhcp3-server launches before upstart brings all interface, thus failing to start -- 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
