Modify the man pages to reflect the addition of a backup

stable restart file, as done by r220510.
This is a content change.

MFC after:	2 weeks

1 files changed, 9 insertions, 5 deletions

diff --git a/usr.sbin/nfsd/stablerestart.5 b/usr.sbin/nfsd/stablerestart.5
index b32b985..7096053 100644
--- a/usr.sbin/nfsd/stablerestart.5
+++ b/usr.sbin/nfsd/stablerestart.5
@@ -24,7 +24,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd December 3, 2009
+.Dd April 10, 2011
 .Dt STABLERESTART 5
 .Os
 .Sh NAME
@@ -75,9 +75,11 @@ 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 -compact
+.Bl -tag -width /var/db/nfs-stablerestart.bak -compact
 .It Pa /var/db/nfs-stablerestart
 NFSv4 stable restart file
+.It Pa /var/db/nfs-stablerestart.bak
+backup copy of the file
 .El
 .Sh SEE ALSO
 .Xr nfsv4 4 ,
@@ -86,8 +88,10 @@ NFSv4 stable restart file
 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. Nfsd will not create the file if it does not
-exist and will simply log a failure to start, in the hopes that the
-file can be recovered from a backup. To move the file, you must edit
+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.