Re: NFS clientaddr, kerberos

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2013-06-23 at 11:35 -0400, James wrote:
> On Sat, 2013-06-22 at 18:42 +0000, Myklebust, Trond wrote:
> > 
> > Kernel parameters cannot be per-namespace; containers don't boot a
> > separate kernel.
> > 
> > Note that if you have compiled nfs as a module, you will want to do
> > something along the lines of:
> > 
> > 	echo "options nfs callback_tcpport=<port>" >>/etc/modprobe.d/options-local.conf
> This is very useful to know.
> Is there any way to specify this as a mount option?

No. The NFSv4 callback channel port number is a global property. It does
not want to be a per-mount thing.

> Will NFSv4.1 silently ignore this and use the same RPC connection if I
> include it for both 4.0, and 4.1 machines?

Yes.


-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux