ITS#3493 checkpoint clarification

diff --git a/doc/man/man5/slapd-bdb.5 b/doc/man/man5/slapd-bdb.5
index 65c5ad57debd39e4394e716a35671048eb5da5a0..ae5dbd530fbdb4964a6a2ffa8b06d8fad87bd933 100644 (file)
--- a/doc/man/man5/slapd-bdb.5
+++ b/doc/man/man5/slapd-bdb.5
@@ -40,21 +40,17 @@ by the BDB backend database instance.
 The default is 1000 entries.
 .TP
 .B checkpoint <kbyte> <min>
-Specify the frequency for checkpointing the database transaction log.
-A checkpoint operation flushes the database buffers to disk and writes
-a checkpoint record in the log.
-The checkpoint will occur if either <kbyte> data has been written or
-<min> minutes have passed since the last checkpoint.
-Both arguments default to zero, in which case they are ignored. Note
-that the checkpoint conditions are only tested after a write operation,
-and not every <min> minutes. As such, data written within <min> minutes
-of the last checkpoint will
-.I not
-get flushed until the next write operation happens after that interval.
-Outstanding writes in this situation may not get flushed if the server
-is shutdown uncleanly, and the database will need to be recovered before
-the next startup.
-See the Berkeley DB reference guide for more details.
+Specify the frequency for checkpointing the database transaction
+log upon updating of the database.  A checkpointing flushes the
+database buffers to disk and writes a checkpoint record in the log.
+Upon a database update, a checkpoint will occur if either <kbyte>
+data has been written or <min> minutes have passed since the last
+checkpoint.  Both arguments default to zero, in which case they are
+ignored.  Note: checkpointing by this directive occurs only upon execution of
+a database update.  If one desires checkpoinging to occur otherwise,
+db_checkpoint(1) or other external process should be used to cause
+a database checkpoint to be taken.  See the Berkeley DB reference
+guide for more details.
 .TP
 .B dbnosync
 Specify that on-disk database contents should not be immediately