stablerestart(5): Fix some issues reported by mandoc

- New sentence, new line
This commit is contained in:
Gordon Bergling 2020-10-22 19:25:01 +00:00
parent 54f09403a3
commit ad5e10ec0c

View File

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