NFS based /usr prevents normal startup due to slow net init

[Mike Meyer]

In <86lki8u1al.fsf at dwp.des.no>, Dag-Erling Smørgrav <des at des.no> typed:
> Mike Meyer <mwm-keyword-freebsdhackers2.e313df at mired.org> writes:
> > Steven Hartland <killing at multiplay.co.uk> writes:
> > > Another observation from my recent dealings with using
> > > NFS based /usr is that the remote critical mounts via
> > > nfs dont always give the network enough time to
> > > initialise before running. The first error displayed
> > > is:
> > > Mounting NFS file systems:mount_nfs: nfs1: hostname nor servname provided, or not known
> > > [...]
> > 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

	<mike
-- 
Mike Meyer <mwm at mired.org>		http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.