git: 096589c1e1db - stable/12 - MFC r368814: nfsv4(4): Fix a few issues reported by mandoc

Gordon Bergling gbe at FreeBSD.org
Sun Dec 27 13:10:37 UTC 2020


The branch stable/12 has been updated by gbe (doc committer):

URL: https://cgit.FreeBSD.org/src/commit/?id=096589c1e1db4c06e2f304682f9335f60da46324

commit 096589c1e1db4c06e2f304682f9335f60da46324
Author:     Gordon Bergling <gbe at FreeBSD.org>
AuthorDate: 2020-12-19 13:45:39 +0000
Commit:     Gordon Bergling <gbe at FreeBSD.org>
CommitDate: 2020-12-27 13:03:59 +0000

    MFC r368814: nfsv4(4): Fix a few issues reported by mandoc
    
    - new sentence, new line
    - function name without markup: rtalloc()
    - function name without markup: VOP_RECLAIM()
    
    (cherry picked from commit 749ddf491b4370300a2edbd47aed9ee1b5d71178)
---
 usr.sbin/nfsd/nfsv4.4 | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/usr.sbin/nfsd/nfsv4.4 b/usr.sbin/nfsd/nfsv4.4
index 82b25a2982b3..af1876463247 100644
--- a/usr.sbin/nfsd/nfsv4.4
+++ b/usr.sbin/nfsd/nfsv4.4
@@ -57,8 +57,8 @@ To provide for correct recovery semantics, a small file described by
 is used by the server during the recovery phase.
 If this file is missing or empty, there is a backup copy maintained by
 .Xr nfsd 8
-that will be used. If either file is missing, they will be
-created by the
+that will be used.
+If either file is missing, they will be created by the
 .Xr nfsd 8 .
 If both the file and the backup copy are empty,
 it will result in the server starting without providing a grace period
@@ -290,7 +290,8 @@ Without a functioning callback path, a server will never issue Delegations
 to a client.
 .sp
 For NFSv4.0, by default, the callback address will be set to the IP address acquired via
-rtalloc() in the kernel and port# 7745.
+.Fn rtalloc
+in the kernel and port# 7745.
 To override the default port#, a command line option for
 .Xr nfscbd 8
 can be used.
@@ -332,8 +333,9 @@ variables.
 .Pp
 NFSv4 mount(s) against exported volume(s) on the same host are not recommended,
 since this can result in a hung NFS server.
-It occurs when an nfsd thread tries to do an NFSv4 VOP_RECLAIM()/Close RPC
-as part of acquiring a new vnode.
+It occurs when an nfsd thread tries to do an NFSv4
+.Fn VOP_RECLAIM
+/ Close RPC as part of acquiring a new vnode.
 If all other nfsd threads are blocked waiting for lock(s) held by this nfsd
 thread, then there isn't an nfsd thread to service the Close RPC.
 .Sh FILES


More information about the dev-commits-src-branches mailing list