The rc.d mess strikes back
Mike Telahun Makonnen
mmakonnen at gmail.com
Tue Mar 3 08:33:42 PST 2009
On Tue, Mar 3, 2009 at 4:15 AM, M. Warner Losh <imp at bsdimp.com> wrote:
> In message: <20090302233215.GA53763 at duncan.reilly.home>
> Andrew Reilly <andrew-freebsd at areilly.bpc-users.org> writes:
> : On Mon, Mar 02, 2009 at 01:25:22PM -0700, M. Warner Losh wrote:
> : > In message: <2fd864e0903020512i22b2c31fg487aaf37fed6398b at mail.gmail.com>
> : > Astrodog <astrodog at 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 doesn'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
> : 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?
More information about the freebsd-current