From: Peter Staubach <staubach@redhat.com>
To: Risto Bell <reb@cypress.com>
Cc: autofs@linux.kernel.org
Subject: Re: autofs Digest, Vol 43, Issue 12
Date: Tue, 31 Oct 2006 13:14:37 -0500 [thread overview]
Message-ID: <4547928D.3070007@redhat.com> (raw)
In-Reply-To: <45478B5A.7000106@cypress.com>
Risto Bell wrote:
> > My system defaults to tcp nfs v3 if no options are specified.
>
> How does one achieve/config that (Solaris like) in autofs4?
> Likewise achieving the NETAPP recommended TCP options timeo=600,retrans=2
>
> If you have mix of servers, some only supporting UDP, but wish
> to prefer TCPv3 whereever it's available and UDP only if no choice...
>
> I use scripts programs (like auto.net), that do rpcinfo
> to test if the server supports TCP and add the options. But even
> emulating NIS look-ups, overall result (scripts) are considerably
> slower.
Perhaps I am missing something, but the default NFS Version 3 over TCP.
If that is not available, then the client falls back to NFS Version 3
over UDP, NFS Version 2 over TCP, and then NFS Version 2 over UDP,
in that order.
As far as I can tell, it should not be necessary to specify any mount
options controlling the NFS protocol version or transport choice, unless
you specifically want it to be a single combination and not allow it to
fall back.
All that extra support is just overhead if the mount command is already
doing the right thing.
Thanx...
ps
next prev parent reply other threads:[~2006-10-31 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1162296001.31020.autofs@linux.kernel.org>
2006-10-31 17:43 ` autofs Digest, Vol 43, Issue 12 Risto Bell
2006-10-31 18:14 ` Peter Staubach [this message]
2007-10-02 21:52 ` autofs-4.1.3-150: Spooky ghosting benefit?: Less HUP's to refresh NIS maps Risto Bell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4547928D.3070007@redhat.com \
--to=staubach@redhat.com \
--cc=autofs@linux.kernel.org \
--cc=reb@cypress.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.