From: Jim Rees <rees@umich.edu>
To: NeilBrown <neilb@suse.de>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: mounting via udp from legacy multi-homed servers...
Date: Wed, 13 Jul 2011 07:08:00 -0400 [thread overview]
Message-ID: <20110713110800.GA25370@merit.edu> (raw)
In-Reply-To: <20110713173426.03576562@notabene.brown>
NeilBrown wrote:
1/ We could use tcp for all rpcbind lookups if tcp was requested for either
MOUNT or NFS.
If I requested tcp for mount and then also got tcp for rpcbind, I would find
that natural and useful.
2/ If '-v' was given and a UDP lookup to portmap timedout, we could retry
without connecting (and with a shorter timeout), and print an explanatory
message if that succeeded.
If '-v' actually changed the behavior of the mount command rather than just
increasing the verbosity I would find that surprising.
next prev parent reply other threads:[~2011-07-13 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 7:34 mounting via udp from legacy multi-homed servers NeilBrown
2011-07-13 11:08 ` Jim Rees [this message]
2011-07-13 11:57 ` Steve Dickson
2011-07-15 22:55 ` Chuck Lever
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=20110713110800.GA25370@merit.edu \
--to=rees@umich.edu \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox