All of lore.kernel.org
 help / color / mirror / Atom feed
From: Risto Bell <reb@cypress.com>
To: autofs@linux.kernel.org
Subject: Re: autofs4: How to confg TCP 1st choice, not UPD?
Date: Wed, 01 Nov 2006 14:48:25 -0800	[thread overview]
Message-ID: <45492439.9020409@cypress.com> (raw)
In-Reply-To: <mailman.122.1162331942.2205.autofs@linux.kernel.org>

Using RedHat Enterprise 3 update 6. Release notes consistent with
my experience that UDP is the default. Perhaps RedHat changed the
default autofs4's natural TCP back to UDP? In any event, question
remains: There isn't an simple config by which to control it (prefer
TCP with timeo=600,retrans=2 1st), it has to be compiled into it?

Also could use multi-mounts? List two alternative mounts, same but
one TCP and one UPD, so the 1st (TCP) will be attempted, and only if
it fails (server doesn't support TCP) will it fall to 2nd (UDP)?
This would still need programs/scripts but would save rcpinfo process,
and achieve slight speed-up.

% egrep -C4 ' autofs-4|NFS.*UDP' RELEASE-NOTES-en RELEASE-NOTES-U6-en
RELEASE-NOTES-en-     o The Red Hat Enterprise Linux 3 kernel now includes support for NFS
RELEASE-NOTES-en-       over TCP. To use NFS over TCP, you must include the "-o tcp" option to
RELEASE-NOTES-en-       mount when mounting the NFS-exported file system on the client system.
RELEASE-NOTES-en-
RELEASE-NOTES-en:       NOTE: The default transport protocol for NFS remains UDP. Use the
RELEASE-NOTES-en-       mount command with the "-o tcp" option to mount an NFS-exported file
RELEASE-NOTES-en-       system using TCP; otherwise, UDP will be used by default.
RELEASE-NOTES-en-
RELEASE-NOTES-en-     o In this kernel, the following command has been added to scan for new
--
RELEASE-NOTES-U6-en-     o anaconda-9.1.5.8-1.RHEL => anaconda-9.1.6.8-1.RHEL
RELEASE-NOTES-U6-en-
RELEASE-NOTES-U6-en-     o anaconda-runtime-9.1.5.8-1.RHEL => anaconda-runtime-9.1.6.8-1.RHEL
RELEASE-NOTES-U6-en-
RELEASE-NOTES-U6-en:     o autofs-4.1.3-130 => autofs-4.1.3-150
RELEASE-NOTES-U6-en-
RELEASE-NOTES-U6-en-     o binutils-2.14.90.0.4-37 => binutils-2.14.90.0.4-39
RELEASE-NOTES-U6-en-
RELEASE-NOTES-U6-en-     o bonobo-activation-2.2.2-1 => bonobo-activation-2.2.2-1.2E

       reply	other threads:[~2006-11-01 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.122.1162331942.2205.autofs@linux.kernel.org>
2006-11-01 22:48 ` Risto Bell [this message]
2006-11-01 23:14   ` autofs4: How to confg TCP 1st choice, not UPD? Jeff Moyer

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=45492439.9020409@cypress.com \
    --to=reb@cypress.com \
    --cc=autofs@linux.kernel.org \
    /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.