From: Jim Rees <rees@umich.edu>
To: linux-nfs@vger.kernel.org
Subject: Re: client using portmap/rpcbind when port options are given?
Date: Wed, 8 Jan 2014 21:00:58 -0500 [thread overview]
Message-ID: <20140109020058.GA8351@umich.edu> (raw)
In-Reply-To: <20140108234258.GA11800@umich.edu>
Jim Rees wrote:
How come my nfs client is trying to contact portmap when I've given both the
port= and mountport= options? Is it supposed to do that? Nfs3, nolock,
kernel 3.12, nfsutils 1.2.9 on Arch.
To answer my own question... you have to specify transport protocol. I had
thought that since tcp is the default, I wouldn't need that option, but I
do.
Thanks everyone for the help.
prev parent reply other threads:[~2014-01-09 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 23:42 client using portmap/rpcbind when port options are given? Jim Rees
2014-01-09 2:00 ` Jim Rees [this message]
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=20140109020058.GA8351@umich.edu \
--to=rees@umich.edu \
--cc=linux-nfs@vger.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.