svn commit: r366949 - head/usr.sbin/nfsd

Gordon Bergling gbe at FreeBSD.org
Thu Oct 22 19:25:02 UTC 2020


Author: gbe (doc committer)
Date: Thu Oct 22 19:25:01 2020
New Revision: 366949
URL: https://svnweb.freebsd.org/changeset/base/366949

Log:
  stablerestart(5): Fix some issues reported by mandoc
  
  - New sentence, new line

Modified:
  head/usr.sbin/nfsd/stablerestart.5

Modified: head/usr.sbin/nfsd/stablerestart.5
==============================================================================
--- head/usr.sbin/nfsd/stablerestart.5	Thu Oct 22 19:22:34 2020	(r366948)
+++ head/usr.sbin/nfsd/stablerestart.5	Thu Oct 22 19:25:01 2020	(r366949)
@@ -52,18 +52,18 @@ first record.
 The lease duration is used to set the grace period.
 The boot times
 are used to avoid the unlikely occurrence of a boot time being reused,
-due to a TOD clock going backwards. This record and the previous boot times with this boot time added is re-written at the
-end of the grace period.
+due to a TOD clock going backwards.
+This record and the previous boot times with this boot time
+added is re-written at the end of the grace period.
 .Pp
 The rest of the file are appended records, as defined by
-struct nfst_rec in /usr/include/fs/nfs/nfsrvstate.h and are used
-represent one of two things. There are records which indicate that a
+struct nfst_rec in /usr/include/fs/nfs/nfsrvstate.h and are used represent one of two things.
+There are records which indicate that a
 client successfully acquired state and records that indicate a client's state was revoked.
 State revoke records indicate that state information
 for a client was discarded, due to lease expiry and an otherwise
 conflicting open or lock request being made by a different client.
-These records can be used
-to determine if clients might have done either of the
+These records can be used to determine if clients might have done either of the
 edge conditions.
 .Pp
 If a client might have done either edge condition or this file is
@@ -71,8 +71,8 @@ empty or corrupted, the server returns NFSERR_NOGRACE 
 request from the client.
 .Pp
 For correct operation of the server, it must be ensured that the file
-is written to stable storage by the time a write op with IO_SYNC specified
-has returned. This might require hardware level caching to be disabled for
+is written to stable storage by the time a write op with IO_SYNC specified has returned.
+This might require hardware level caching to be disabled for
 a local disk drive that holds the file, or similar.
 .Sh FILES
 .Bl -tag -width /var/db/nfs-stablerestart.bak -compact
@@ -86,12 +86,11 @@ backup copy of the file
 .Xr nfsd 8
 .Sh BUGS
 If the file is empty, the NFSv4 server has no choice but to return
-NFSERR_NOGRACE for all reclaim requests. Although correct, this is
-a highly undesirable occurrence, so the file should not be lost if
-at all possible. The backup copy of the file is maintained
-and used by the
+NFSERR_NOGRACE for all reclaim requests.
+Although correct, this is a highly undesirable occurrence, so the file should not be lost if
+at all possible.
+The backup copy of the file is maintained and used by the
 .Xr nfsd 8
 to minimize the risk of this occurring.
-To move the file, you must edit
-the nfsd sources and recompile it. This was done to discourage
-accidental relocation of the file.
+To move the file, you must edit the nfsd sources and recompile it.
+This was done to discourage accidental relocation of the file.


More information about the svn-src-all mailing list