From owner-freebsd-current@FreeBSD.ORG Thu Jul 7 00:57:55 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 304B61065672 for ; Thu, 7 Jul 2011 00:57:55 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id E83D58FC12 for ; Thu, 7 Jul 2011 00:57:54 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAEUDFU6DaFvO/2dsb2JhbABTEIQypES7HJBogSuDf4ENBJJBkAZT X-IronPort-AV: E=Sophos;i="4.65,490,1304308800"; d="scan'208";a="126287930" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 06 Jul 2011 20:57:53 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 015A7B3F0F; Wed, 6 Jul 2011 20:57:54 -0400 (EDT) Date: Wed, 6 Jul 2011 20:57:53 -0400 (EDT) From: Rick Macklem To: Steve Kargl Message-ID: <167246498.291336.1310000273959.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20110706235733.GA71278@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) 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:57:55 -0000 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'. > Assuming you've upgraded your /etc/rc.d scripts to those in head, then try deleting /etc/rc.d/nfsserver. (This script just tries to load the old server even though you don't need it unless you want to run the old one.) Or you can build a kernel with both options NFSD options NFSSERVER to make it happy. I'll try posting to rc@ to see if I can get rid of /etc/rc.d/nfsserver. Thanks for pointing this out. I had forgotten about deleting this (and was until recently confused about when obsolete files get deleted). If you still have problems after deleting /etc/rc.d/nfsserver (assuming your /etc/rc.d scripts are up-to-date), please let me know. rick