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. =A0In doing so, I changed the kernel config
> options from
>
> options =A0 =A0 =A0 =A0 NFSCLIENT =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Network F=
ilesystem Client
> options =A0 =A0 =A0 =A0 NFSSERVER =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Network F=
ilesystem Server
>
> to
>
> options =A0 =A0 =A0 =A0 NFSCL =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# Network Fi=
lesystem Client
> options =A0 =A0 =A0 =A0 NFSD =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Network Fi=
lesystem Server
>
> rebuild and install the kernel. =A0Upon rebooting, I'm greeted
> with a
>
> Jul =A06 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. =A0So, why is the system trying to load a nfsserver
> module? =A0Because, my /etc/rc.conf contains
>
> nfs_client_enable=3D"YES"
> nfs_server_enable=3D"YES"
>
> if I change this to
>
> nfs_client_enable=3D"YES"
> nfsv4_server_enable=3D"YES"
>
> The system no longer tries to load nfsserver upon rebooting.
> Unfortunately, this has the effect that no nfsd daemons are
> started. =A0Well, 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
..
Cheers!
-Garrett
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"