Date: Sun, 26 Feb 2006 13:30:10 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Tobias Roth <roth@iam.unibe.ch> Cc: freebsd-rc@freebsd.org Subject: Re: dhclient existing when run early in startup Message-ID: <44021DE2.2010509@FreeBSD.org> In-Reply-To: <20060225132226.GA27397@droopy.unibe.ch> References: <20060221023750.GA32185@odin.ac.hmc.edu> <20060221045324.8717645048@ptavv.es.net> <20060221075140.GA9101@droopy.unibe.ch> <20060221212818.GA22713@odin.ac.hmc.edu> <20060225132226.GA27397@droopy.unibe.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
Tobias Roth wrote: > On Tue, Feb 21, 2006 at 01:28:18PM -0800, Brooks Davis wrote: > >>> Possible improvements: >>> 1) change dhclient to accept a timeout on the commandline >> This would be a useful addon. Actually, I'd like to see both the option >> to specify a shorter one and the option to keep trying forever since >> that's what's wanted in some scenerios. > > I've implemented the two switches -i and -t, that override the variables > from dhclient.conf 'retry' and 'timeout'. The patch can be found here: > > http://fsck.ch/dhclient_timeouts.diff While you're at it, how about making the number of tries a runtime option as well? I'm speaking specifically about the number of times dhclient tries an interface before giving up with 'no link'. I have locally patched my system to reduce that number from 10 to 5 since on my laptop bge0 is always tried first, and rarely is it actually connected. Doug -- This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44021DE2.2010509>