During boot time network services are launched before ifplugd

[aledin]

ifplugd, in the init's boot process, have to be runned before the scripts that do networking task (as ntpdate)

ifplugd, in the init's boot process, have to be runned before the scripts that do networking task (as ntpdate). But ifplugd package of hoary has a too high init level for the /etc/init.d/ifplugd script, so it's runned after /etc/init.d/networking and /etc/init.d/ntpdate. In this way, ntpdate can't reach the network because ifplugd isn't yet called.

[skippy (skippy)]

I removed the package's default rc?.d symlinks and created /etc/rcS.d/S42ifplugd to solve this problem. I agree that ifplugd should execute shortly after networking is started, so that later startup items can make use of the network if available.

I installed ifplugd specifically to avoid ntpdate causing delays at boot when no network cable is installed.

[Scott James Remnant (Canonical) (canonical-scott)]

I'm not convinced this will fix it, given that the network device in dapper is bought up by udev at S10 (and there's no network device module loaded before that)

[Wouter Stomp (wouterstomp-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Sergio Zanchetta (primes2h)]

This bug was opened againt Hoary and no feedback given. Closing.