Date: Wed, 6 Jul 2011 21:07:46 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Garrett Cooper <yanegomi@gmail.com>, freebsd-current@freebsd.org Subject: Re: Can options NFSD and NFSSERVER exist in the same kernel? Message-ID: <455800269.291497.1310000866965.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20110707001411.GA71351@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote: > On Wed, Jul 06, 2011 at 05:02:37PM -0700, Garrett Cooper wrote: > > On Wed, Jul 6, 2011 at 4:57 PM, Steve Kargl > > <sgk@troutmask.apl.washington.edu> 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. > With -current /etc/rc.d/nfsd and /etc/rc.d/mountd, you shouldn't need to set nfsv4_server_enable="YES". The latter is only needed if you want to support NFSv4. I agree that /etc/rc.d/nfsserver will still try to load the old nfs server if it isn't built into the kernel and I'll look at getting rid of it. I was also trying to minimize the churn in head in case it was necessary to revert the change in default. I'm not sure that an upgrade that doesn't include building and installing new modules can be expected to work correctly when taken off of head when headed (no pun intended) into a major release. However, it is good that you reported this, so the /etc/rc.d/nfsserver issue can get resolved. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?455800269.291497.1310000866965.JavaMail.root>