From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 00:08:32 2010 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 6A95E1065674 for ; Sun, 12 Sep 2010 00:08:32 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 4C4AF8FC08 for ; Sun, 12 Sep 2010 00:08:31 +0000 (UTC) Received: from [10.123.2.180] (DIR-655 [192.168.1.65]) by monday.kientzle.com (8.14.3/8.14.3) with ESMTP id o8C08Vfd011559; Sun, 12 Sep 2010 00:08:31 GMT (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <579405651.776013.1284247201493.JavaMail.root@erie.cs.uoguelph.ca> Date: Sat, 11 Sep 2010 17:08:30 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <579405651.776013.1284247201493.JavaMail.root@erie.cs.uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.1081) Cc: freebsd-current@freebsd.org Subject: Re: Experimental NFS server oddity 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, 12 Sep 2010 00:08:32 -0000 On Sep 11, 2010, at 4:20 PM, Rick Macklem wrote: >> I just tried adding >>=20 >> nfsv4_server_enable=3D"YES" >>=20 >> to my rc.conf and found that after I rebooted the server, my FreeBSD = 8 >> client (still using NFSv3) couldn't connect because there was no RPC >> mapping for nfs. > Did you specify both of these in rc.conf? > nfs_server_enable=3D"YES" > nfsv4_server_enable=3D"YES" >=20 > You need to specify both of them (and nfsuserd=3D"YES" if you going to = use > NFSv4). See "man nfsv4" for more. Both specified, as well as rpcbind_enable=3D"YES" > If you did specify both, then do a "ps axHl" to see what didn't start = up. rpcbind, mountd, and nfsuserd are all running, but nfsd is not running. > You can also look in /var/log/messages to see if any of the daemons > are complaining about something. Only warning I see on a system reboot is: nfsd: can't open /var/db/nfs-stablerestart Creating this file and then rebooting the system seems to get things = working. This file certainly wasn't required by the old nfsd. Should this file be created by /etc/rc.d/nfsserver at boot time (if it = doesn't exist)? Or should it be created by installworld? Tim