From owner-freebsd-current@FreeBSD.ORG Thu Jul 7 00:14:11 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 F35F7106566C for ; Thu, 7 Jul 2011 00:14:11 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id CF87A8FC12 for ; Thu, 7 Jul 2011 00:14:11 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id p670EBVo071476; Wed, 6 Jul 2011 17:14:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id p670EB0U071475; Wed, 6 Jul 2011 17:14:11 -0700 (PDT) (envelope-from sgk) Date: Wed, 6 Jul 2011 17:14:11 -0700 From: Steve Kargl To: Garrett Cooper Message-ID: <20110707001411.GA71351@troutmask.apl.washington.edu> References: <20110706235733.GA71278@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Can options NFSD and NFSSERVER exist in the same kernel? 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: Thu, 07 Jul 2011 00:14:12 -0000 On Wed, Jul 06, 2011 at 05:02:37PM -0700, Garrett Cooper wrote: > On Wed, Jul 6, 2011 at 4:57 PM, Steve Kargl > wrote: > > So, I upgraded a system from Feb 10 -current to today's > > -current code. ?In doing so, I changed the kernel config > > options from > > > > options ? ? ? ? NFSCLIENT ? ? ? ? ? ? ? # Network Filesystem Client > > options ? ? ? ? NFSSERVER ? ? ? ? ? ? ? # Network Filesystem Server > > > > to > > > > options ? ? ? ? NFSCL ? ? ? ? ? ? ? ?# Network Filesystem Client > > options ? ? ? ? NFSD ? ? ? ? ? ? ? ? # Network Filesystem Server > > > > rebuild and install the kernel. ?Upon rebooting, I'm greeted > > with a > > > > Jul ?6 16:09:41 node16 root: /etc/rc: WARNING: Unable to load > > kernel module nfsserver > > > > Of course, it can't load nfsserver because I don't use modules > > nor build them. ?So, why is the system trying to load a nfsserver > > module? ?Because, my /etc/rc.conf contains > > > > nfs_client_enable="YES" > > nfs_server_enable="YES" > > > > if I change this to > > > > nfs_client_enable="YES" > > nfsv4_server_enable="YES" > > > > The system no longer tries to load nfsserver upon rebooting. > > Unfortunately, this has the effect that no nfsd daemons are > > started. ?Well, I can start the daemons post-booting. > > > > node16:root[139] /etc/rc.d/nfsd start > > Cannot 'start' nfsd. Set nfs_server_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'. > > Try nfsserver instead of nfsd. Here's the archived discussion of > my foray into this territory a few months ago: > http://www.mailinglistarchive.com/html/freebsd-current@freebsd.org/2011-05/msg00008.html > . Thanks for the pointer. Note, the 20110427 src/UPDATING entry indicates the NFSSERVER has been changed to NFSD in GENERIC. It seems that one needs to have both nfs_server_enable and nfsv4_server_enable set to "YES" in rc.conf to get nfsd daemons started. This is POLA violation for anyone upgrading from pre-20110427 -current and carrying over their old /etc/rc.conf. -- Steve