The rc.d mess strikes back

[Astrodog]

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.

--- Harrison

On Mon, Mar 2, 2009 at 6:19 AM, Mike Makonnen <mmakonnen at gmail.com> wrote:
> Garrett Cooper wrote:
>>>
>>> :     Could we just unwind this rc.d mess? It seems to be causing issues
>>> : and wasn't very thoroughly tested before commit.
>>>
>
> This is not an option because the previous behavior caused an unconditional
> 30 sec. delay if the system wasn't plugged in (or if it is plugged in but
> not on a DHCP network).  I think making synchronous_dhclient default to YES
> is the best option.
>
> Cheers.
> --
> Mike Makonnen       | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc
> mtm @ FreeBSD.Org   | AC7B 5672 2D11 F4D0 EBF8  5279 5359 2B82 7CD4 1F55
> FreeBSD             | http://www.freebsd.org
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>



-- 
"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects."
--- Robert A. Heinlein