From owner-freebsd-current@FreeBSD.ORG Sun Jan 9 20:01:34 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 991C11065670 for ; Sun, 9 Jan 2011 20:01:34 +0000 (UTC) (envelope-from salwerom@iem.pw.edu.pl) Received: from volt.iem.pw.edu.pl (volt.iem.pw.edu.pl [194.29.146.3]) by mx1.freebsd.org (Postfix) with SMTP id 30ABD8FC1A for ; Sun, 9 Jan 2011 20:01:33 +0000 (UTC) Received: from [127.0.0.1] (cwx170.internetdsl.tpnet.pl [83.19.131.170]) (Authenticated sender: salwerom) by volt.iem.pw.edu.pl (Postfix) with ESMTPSA id C23BEA66A5B; Sun, 9 Jan 2011 21:01:20 +0100 (CET) Message-ID: <4D2A140C.9020204@iem.pw.edu.pl> Date: Sun, 09 Jan 2011 21:01:16 +0100 From: Marek Salwerowicz User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; pl; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Rick Macklem References: <715043409.18716.1294599583344.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <715043409.18716.1294599583344.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.96.5 at volt.iem.pw.edu.pl X-Virus-Status: Clean X-Mailman-Approved-At: Mon, 10 Jan 2011 01:32:43 +0000 Cc: freebsd-current@freebsd.org, Andrzej Tobola Subject: Re: NFSv4 and pam_mount - mounting user home directories. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2011 20:01:34 -0000 > 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