Date: Sun, 09 Jan 2011 21:01:16 +0100 From: Marek Salwerowicz <salwerom@iem.pw.edu.pl> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-current@freebsd.org, Andrzej Tobola <ato@iem.pw.edu.pl> Subject: Re: NFSv4 and pam_mount - mounting user home directories. Message-ID: <4D2A140C.9020204@iem.pw.edu.pl> In-Reply-To: <715043409.18716.1294599583344.JavaMail.root@erie.cs.uoguelph.ca> References: <715043409.18716.1294599583344.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> Again, it works for me (using a pretty current FreeBSD client). The > only difference is that I never run mount_nfs directly and would use > the following command: > > # mount -t nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4 > > Assuming the client is a FreeBSD8 box on the 192.168.183.0 subnet, > I don't know why it wouldn't work, except that I'd suggest trying > the command the way I type it, in case that runs it with somewhat > different options? > > rick So, I added in /etc/rc.conf: rpcbind_enable=YES reboot and again typed the commands above. and now it seems to WORK ;) : nfs4-client# mount -t nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4 nfs4-client# mount -t newnfs 192.168.183.131:/home on /tmp/nfs4 (newnfs) nfs4-client# umount /tmp/nfs4 nfs4-client# mount -t nfs 192.168.183.131:/usr/home /tmp/nfs3 [tcp] 192.168.183.131:/usr/home: NFSPROC_NULL: RPC: Program/version mismatch; low version = 4, high version = 4 ^C nfs4-client# with mount_nfs command it behaves the same. Good to know if it will work with nfsv4 server started via rc.conf and sysctl values in sysctl.conf.. -- Marek Salwerowicz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D2A140C.9020204>