Date: Thu, 08 Mar 2007 08:25:55 +0100 From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Mike Meyer <mwm@mired.org> Cc: freebsd-hackers@freebsd.org, Steven Hartland <killing@multiplay.co.uk> Subject: Re: NFS based /usr prevents normal startup due to slow net init Message-ID: <86fy8gw60s.fsf@dwp.des.no> In-Reply-To: <17903.37547.207909.316479@bhuda.mired.org> (Mike Meyer's message of "Wed, 7 Mar 2007 23:35:55 -0500") References: <015601c75ce9$d0263a10$b3db87d4@multiplay.co.uk> <17896.23312.980989.68558@bhuda.mired.org> <86lki8u1al.fsf@dwp.des.no> <17903.37547.207909.316479@bhuda.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Meyer <mwm@mired.org> writes: > Dag-Erling Sm=F8rgrav <des@des.no> writes: > > Mike Meyer <mwm-keyword-freebsdhackers2.e313df@mired.org> writes: > > > How about an extra flag in your fstab? The default behavior for > > > mount_nfs is to keep retrying until the mount succeeds. > > No, it will fail immediately (as seen above) if it can't resolve the > > server name. The only way to fix this is to modify mount_nfs to sleep > > and retry in such cases. The *current* sleep-and-retry code is in the > > NFS mount code in the kernel, which doesn't come into play until after > > DNS lookup. > In that case, there's a bug in the mount_nfs man page, which just says > that it keeps retrying until it succeeds. PR #110062 Technically, that's correct if you specify the server by IP address or have it listed in /etc/hosts... but I guess the man page could be clearer. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86fy8gw60s.fsf>