From: Oren Held <oren@held.org.il>
To: nfs@lists.sourceforge.net
Subject: try tcp first; then udp
Date: Sat, 01 Nov 2003 17:34:49 +0200 [thread overview]
Message-ID: <1067700887.5055.4.camel@localhost> (raw)
Hi,
I wonder if there's a way to mount an nfs share without specifying tcp
or udp mount. I think that this is how Solaris behaves: it tries first
tcp, if it's not good, then it tries udp.
I've been looking for such a mount option and found none; I think it can
be really useful when one has hetrogenous nfs servers (some use tcp,
some use udp) - in the case I just want it to work and don't care which
protocol it'll use.
Is there a way to do it with the current kernel/mount versions?
10x
- Oren
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-11-01 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 15:34 Oren Held [this message]
2003-11-03 12:01 ` try tcp first; then udp James Pearson
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=1067700887.5055.4.camel@localhost \
--to=oren@held.org.il \
--cc=nfs@lists.sourceforge.net \
/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.