In <[EMAIL PROTECTED]>, Dag-Erling Smørgrav <[EMAIL PROTECTED]> typed:
> Mike Meyer <[EMAIL PROTECTED]> writes:
> > Steven Hartland <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
