Bug 163488

Summary: Confusing explanation in defaults/rc.conf
Product: Base System Reporter: Peter <freebsd>
Component: confAssignee: freebsd-bugs (Nobody) <bugs>
Status: Open ---    
Severity: Affects Only Me    
Priority: Normal    
Version: 9.0-PRERELEASE   
Hardware: Any   
OS: Any   

Description Peter 2011-12-20 19:50:11 UTC
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'.
'# Force old non NFSv4 server'


Change defaults/rc.conf one liner to resemble 'man nfsd' terminology.
How-To-Repeat: grep "nfs.*server_enable" defaults/rc.conf
man nfsd|grep -A 1 -- -o
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2011-12-24 02:02:42 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-rc

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:13 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped