>Number: 163488
>Category: conf
>Synopsis: Confusing explanation in defaults/rc.conf
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Dec 20 19:50:11 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator: Peter
>Release: FreeBSD 9.0-PRERELEASE #0 r228292
>Organization:
>Environment:
FreeBSD pkbsd.pk.pb 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0 r228292: Mon Dec
5 16:20:40 MST 2011 r...@pkbsd.pb.com:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
pkbsd:#grep "nfs.*server_enable" defaults/rc.conf
nfs_server_enable="NO" # This host is an NFS server (or NO).
oldnfs_server_enable="NO" # Run the old NFS server (YES/NO).
nfsv4_server_enable="NO" # Enable support for NFSv4
It took me a bit to trace exactly what happens when both these options are set
to "NO" in defaults/rc.conf - Which one is started? Initially I figured nfsv4
is started as oldnfs is set to NO, but then nfsv4 was also set to NO. Only
after looking through /etc/rc.d/nfsd and then looking at 'man nfsd' and the
'-o' option did that clear it up.
-o Forces the use of the old NFS server that does not include NFSv4
support in it.
Maybe instead of '# Run the old NFS server (YES/NO).' [Sounds like "run nfsv3"]
put in '# Force old NFSv3 only server (YES/NO)' - More inline/same terminology
as the man page for 'nfsd'.
or
'# Force old non NFSv4 server'
>How-To-Repeat:
grep "nfs.*server_enable" defaults/rc.conf
man nfsd|grep -A 1 -- -o
>Fix:
Change defaults/rc.conf one liner to resemble 'man nfsd' terminology.
>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
