Date: Wed, 4 Mar 2009 10:49:53 -0600 From: Brooks Davis <brooks@freebsd.org> To: Garrett Cooper <yanefbsd@gmail.com> Cc: andrew-freebsd@areilly.bpc-users.org, astrodog@gmail.com, Mike Telahun Makonnen <mmakonnen@gmail.com>, usb@freebsd.org, freebsd-current@freebsd.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: The rc.d mess strikes back Message-ID: <20090304164953.GB1209@lor.one-eyed-alien.net> In-Reply-To: <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com> <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> <20090303180307.GA11134@lor.one-eyed-alien.net> <584bfc3f0903032212x25831c5bi35d9b637c1896e1d@mail.gmail.com> <7d6fde3d0903040004y1fcbb086i355cd0113717620b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--rJwd6BRFiFCcLxzm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 04, 2009 at 12:04:06AM -0800, Garrett Cooper wrote: > On Tue, Mar 3, 2009 at 10:12 PM, Mike Telahun Makonnen > <mmakonnen@gmail.com> wrote: > > On Tue, Mar 3, 2009 at 9:03 PM, Brooks Davis <brooks@freebsd.org> wrote: > >> > >> I don't have much time to debug this, but I've not had problems with > >> services starting too early on the systems I've been running with async > >> dhcp. ?If there is a problem with the wait process we need to actually > >> debug it. ?If the wait for a route/running interface isn't sufficent we > >> should try to figure out what is. ?Synchronous dhcp sucks and yeilds > >> justifed user complaints so it would be nice to kill it off. ?I switch= ed > >> the default because it worked for me and I hoped that people would help > >> find and fix edge cases. > > > > Can you elaborate why synchronous DHCP sucks ? >=20 > The only reason I could see is bringup time. Am I correct in this assumpt= ion? If you use synchronous DHCP then every interface that wants to try to get a DHCP address if it has link needs to run through the full link timeout at boot. On a laptop this is annoying and generally pointless. The changes to defaultroute to wait for a default route to be set mean that you consolidate the wait in one location and you don't waste time starting dhclient on interfaces until a link exists (or an association is made for wlan devices). There may well be something better to wait or a need for a longer timeout in some environments. It's also quite possible that we have an ordering problem and need to move some more things after defaultroute or move the checks to a different location. -- Brooks --rJwd6BRFiFCcLxzm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFJrrEwXY6L6fI4GtQRAlPtAKCbIwm4d9bKGwnzXQzWtfx+RsjZDQCgqzCf 1MVkBETW0iL4socEznZBkyM= =0Anm -----END PGP SIGNATURE----- --rJwd6BRFiFCcLxzm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090304164953.GB1209>