From owner-freebsd-stable@FreeBSD.ORG Thu May 26 22:34:38 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id A8A3C106564A for ; Thu, 26 May 2011 22:34:38 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 6B6691525A1; Thu, 26 May 2011 22:34:37 +0000 (UTC) Message-ID: <4DDED57B.5040802@FreeBSD.org> Date: Thu, 26 May 2011 15:34:35 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10 MIME-Version: 1.0 To: William Palfreman References: In-Reply-To: X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: mountlate not late enough for nfe0 with dhcp X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 22:34:38 -0000 On 05/26/2011 14:35, William Palfreman wrote: > I do think that it would be better if failure to mount an NFS share due > to DHCP not being finished did not cause the boot to halt. Non-root > filesystem NFS mounts are rarely so critical that is it necessary to drop > into single user mode instead - especially as these days many machines do > not have a console continuously attached. It would be better just to retry > mounting NFS in the background. If having DHCP up before proceeding is mission critical, set the synchronous_dhclient option in rc.conf. If you are satisfied with having the nfs mounts continue in the background, use that option in fstab. In the absence of those 2 clear indications from the admin as to what should happen, the current behavior is the right choice. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/