I switched locations this evening, and again the short timeout bit me. I played with several times in /etc/sysconfig/network/dhcp... Neither reducing nor increasing DHCLIENT_TIMEOUT seemed to have an effect, but increasing DHCLIENT_REBOOT_TIMEOUT to 15 gave me anough time. At least at this location, I got a response in 4 seconds. We'll see if it continues to work at other locations... Rick Green On Tue, 4 Jun 2002, Jerry Feldman wrote:
Lately, I also have been having some wierdness with dhcpcd. The problem is that on startup, the client would receive a NAK and terminate. By popping the card or restarting pcmcia, it would eventually fire up.
There is a file in /etc/sysconfig/network/dhcp which contains some elements. (YaST2 system admin/sysconfig editor/etc is probably the best place to do this). I commented out DHCLIENT_TIMEOUT, which sets the -t option. The default is 60 seconds, the value in the script is 999999. This worked, so I then restored it and turned on debug. It appears that simply turning on debug masks the problem.
My recommendation is to use YaST2, turn on debug first, then you might adjust some of the flags.
Remember, in 8.0, the location and functions of some of the scripts were changed to comply with LSB. -- Jerry Feldman Enterprise Systems Group Hewlett-Packard Company 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752 508-467-4315 http://www.testdrive.compaq.com/linux/