Date: Wed, 27 Jul 2005 17:23:23 -0400 From: David Gilbert <dgilbert@dclg.ca> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: Mike Jakubik <mikej@rogers.com>, Doug Barton <dougb@freebsd.org>, Peter Wemm <peter@freebsd.org>, freebsd-current@freebsd.org, David Gilbert <dgilbert@dclg.ca> Subject: Re: dhclient sucks Message-ID: <17127.64331.366734.881214@canoe.dclg.ca> In-Reply-To: <20050727201332.GA23927@odin.ac.hmc.edu> References: <42E583F9.3070703@rogers.com> <200507261853.07513.peter@wemm.org> <1242.172.16.0.199.1122429678.squirrel@172.16.0.1> <200507271215.14369.doconnor@gsoft.com.au> <42E6F5EA.7030801@samsco.org> <42E71F77.6010705@FreeBSD.org> <17127.41923.312257.159166@canoe.dclg.ca> <20050727201332.GA23927@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Brooks" == Brooks Davis <brooks@one-eyed-alien.net> writes: Brooks> On Wed, Jul 27, 2005 at 11:09:55AM -0400, David Gilbert wrote: >> The ISC dhclient would probe multiple interfaces simultaneously. >> The new one waits for some amount o ftime on my hardwire ethernet >> (rarely used) before probing my wireless. The result is a longer >> startup. Brooks> Try: Brooks> background_dhclient="YES" That's an entirely different behaviour. The stock behaviour of ISC is the only sensible behaviour: Wait until either a timeout or you have an address, then continue. It makes the startup scripts happy, and it doesn't waste time. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17127.64331.366734.881214>