Bugzilla – Bug 147658
boot waits for ifplugd devices
Last modified: 2006-02-03 12:37:09 UTC
the booting process waits for ifplugd devices to come up, which can take a long time if no cable is conneced or there is no DHCP running.
It should only wait, if a cable is currenetly connected. Was it connected in your case?
no, its not connected.
it says: Waiting for mandatory devices: eth-id-00:0d:60:89:ba:0b __NSC__ 17 16 14 13 eth2 device: Intel Corporation 82540EP Gigabit Ethernet Controller (Mobile) (rev 03) eth2 configuration: eth-id-00:0d:60:89:ba:0b eth2 ifplugd is running eth2 no cable connected eth2 DHCP client NOT running done modem0 modem0 Startmode is 'manual' skippedSetting up service network . . . . . . . . . . . . . . . .done
Everything is fine. Works as expected. You may change the behavior with /etc/sysconfig/network/config:MANDATORY_DEVICES rcnetwork waits until the interface is available starts ifplugd and finishes. Only if a cable were plugged it would stay waiting until dhcp client is ready or went to background.
$ grep MANDA /etc/sysconfig/network/config MANDATORY_DEVICES=""
grep -B4 MANDA /etc/sysconfig/network/config
how much sense does it make to treat ifplugd not as hotplug devices?
this is a change from previous behaviour btw