Date: Tue, 3 Mar 2009 19:33:39 +0300 From: Mike Telahun Makonnen <mmakonnen@gmail.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: usb@freebsd.org, andrew-freebsd@areilly.bpc-users.org, freebsd-current@freebsd.org, astrodog@gmail.com, yanefbsd@gmail.com Subject: Re: The rc.d mess strikes back Message-ID: <584bfc3f0903030833k70405609q7e2d3b28c8cf4c29@mail.gmail.com> In-Reply-To: <20090302.181513.1973603215.imp@bsdimp.com> References: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.com> <20090302.132522.-432836388.imp@bsdimp.com> <20090302233215.GA53763@duncan.reilly.home> <20090302.181513.1973603215.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 3, 2009 at 4:15 AM, M. Warner Losh <imp@bsdimp.com> wrote: > In message: <20090302233215.GA53763@duncan.reilly.home> > =A0 =A0 =A0 =A0 =A0 =A0Andrew Reilly <andrew-freebsd@areilly.bpc-users.or= g> writes: > : On Mon, Mar 02, 2009 at 01:25:22PM -0700, M. Warner Losh wrote: > : > In message: <2fd864e0903020512i22b2c31fg487aaf37fed6398b@mail.gmail.c= om> > : > =A0 =A0 =A0 =A0 =A0 =A0 Astrodog <astrodog@gmail.com> writes: > : > : As unfortunate (and annoying) as that delay was, your system was in= a > : > : "defined" state, at the end of rc.d. As things stand now, that does= n't > : > : appear to be the case anymore, and I think that may be a more > : > : significant issue than the delay. > : > > : > I'd be happy with synchronous dhcp. Ok. I've been waiting to see if brooks@ was going to weigh in on this, but I'll go ahead and make the change now and see if there is any more fall-out. Once that's done, network behaviour should be more or less the same as before my change, with the exception that any DHCP interfaces that aren't plugged in may delay the boot by more than 30sec. [snip] > > : Needing synchronous DHCP as a work-around here is just the > : signifier of the problem: it isn't the over-all solution. > > It is a short-term work-around at best. >From the problems that have been reported so far it seems to me the problem is with some drivers that repeatedly bring the network link up and down. The *ideal* solution seems (to me) to be to fix these drivers. Am I wrong? Cheers. Mike.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?584bfc3f0903030833k70405609q7e2d3b28c8cf4c29>