Subj : Re: Bringing up interface eth0 (slow) To : comp.os.linux From : rdgentry1 Date : Sat Aug 07 2004 08:37 am "SUCKER [Pieter Van Nuffel]" wrote in message news:<20040807123356.17116668.sucker_pvn@hotmail.com>... > My PC (with Mandrake 10 Official) should boot normally trying to get a > dhcp network address. No problem there, only sometimes I forget to plug > in the power of our switch at home, so it's delayed like 10-15 seconds > and that's extremely annoying. The booting just stops there until the > network is ok. > > Now with my latest knoppix cd (3.4 series) the networking seems smart > enough to do it while 'backgrounding' that stuff. > > Is there a way for letting my network-initializing scripts doing this? From other posts, I thought ifplugd was part of the standard startup scripts on mdk10. You can check /var/log/messages to see how ethX is coming up -- likely something along these lines: network: Setting network parameters: succeeded network: Bringing up loopback interface: succeeded ifplugd(eth0)[681]: ifplugd 0.21b initializing. ifplugd(eth0)[681]: Using interface eth0/00:00:00:00:3D:17 with driver (version: 1.36.4) ifplugd(eth0)[681]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. dhclient: DHCPOFFER from 192.168.0.23 dhclient: DHCPACK from 192.168.0.23 ifplugd(eth0)[681]: client: Determining IP information for eth0... done. ifplugd(eth0)[681]: Program executed successfully. ifplugd(eth0)[681]: Exiting. Can't remember offhand what the timeouts are for ifplugd or if they can be adjusted -- don't use mdk. I think it's the Network Hotplugging feature. It's intended for laptops mostly -- it polls the status of the interface to detect whether its cable is connected and if so keeps trying to connect to the network / DHCP server. My guess is, that since you do have a cable connected, it keeps trying -- during boot -- to connect. Normally, without ifplugd my machine won't timeout till 30-45 seconds have passed. The Knoppix scripts may be using a shorter timeout, continue booting the OS, then once up periodically running ifup if the interface is down -- maybe it tries this for a certain number of tries or time, 10 minutes say. Just a guess here. You might try to compare the ifup scripts in mdk and Knoppix to see if you locate the code (or a clue of where it's at) you could incorporate into mdk's ifup script. Besides the mdk documentation you can try googling or go the ifplugd home page: http://0pointer.de/lennart/projects/ifplugd/ hth, prg email above disabled .