Date: Mon, 02 Mar 2009 15:19:26 +0300 From: Mike Makonnen <mmakonnen@gmail.com> To: Garrett Cooper <yanefbsd@gmail.com> Cc: usb@freebsd.org, freebsd-current@freebsd.org Subject: Re: Re: The rc.d mess strikes back Message-ID: <49ABCECE.1040102@gmail.com> In-Reply-To: <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com> References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> <E39D3873-3F36-467A-B225-347A088B68F9@gmail.com> <20090301.205017.1025328203.imp@bsdimp.com> <2E9BD549-EF77-4F48-AB7E-C93AFC4BE387@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49ABCECE.1040102>