* client using portmap/rpcbind when port options are given?
@ 2014-01-08 23:42 Jim Rees
2014-01-09 2:00 ` Jim Rees
0 siblings, 1 reply; 2+ messages in thread
From: Jim Rees @ 2014-01-08 23:42 UTC (permalink / raw)
To: linux-nfs
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.
Not asking for help debugging this, just asking if this is normal.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: client using portmap/rpcbind when port options are given?
2014-01-08 23:42 client using portmap/rpcbind when port options are given? Jim Rees
@ 2014-01-09 2:00 ` Jim Rees
0 siblings, 0 replies; 2+ messages in thread
From: Jim Rees @ 2014-01-09 2:00 UTC (permalink / raw)
To: linux-nfs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-01-09 2:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-08 23:42 client using portmap/rpcbind when port options are given? Jim Rees
2014-01-09 2:00 ` Jim Rees
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox