ovdb_monitor: Document the frequency of actions

doc/pod/ovdb.pod

@@ -125,7 +125,8 @@ already-established database.  Default is C<32>.
 If txn_nosync is set to false, S<Berkeley DB> flushes the log after every
 transaction.  This minimizes the number of transactions that may be lost
 in the event of a crash, but results in significantly degraded
-performance.  Default is true.
+performance.  Default is true, in which case B<ovdb_monitor> flushes the
+transaction logs every 30 seconds.
 
 =item I<useshm>
 

doc/pod/ovdb_monitor.pod

@@ -10,8 +10,9 @@ Use B<ovdb_init> to start B<ovdb_monitor>
 
 When started (normally by B<ovdb_init> that is invoked by B<rc.news>),
 B<ovdb_monitor> forks three processes that perform routine database
-maintenance tasks.  These are transaction checkpointing, deadlock
-detection, and transaction log removal.
+maintenance tasks.  These are transaction checkpointing (every 30 seconds),
+deadlock detection (every 30 seconds), and transaction log removal (every 45
+seconds).
 
 The process ID of the parent is written to F<ovdb_monitor.pid> in the
 I<pathrun> directory.  This PID is used by other INN commands to verify

samples/ovdb.conf

@@ -35,7 +35,8 @@
 # If txn_nosync is set to false, Berkeley DB flushes the log after every
 # transaction.  This minimizes the number of transactions that may be
 # lost in the event of a crash, but results in significantly degraded
-# performance.  Default is true.
+# performance.  Default is true (in which case ovdb_monitor flushes the
+# transaction logs every 30 seconds).
 #txn_nosync     true
 
 # If useshm is set to true, Berkeley DB will use shared memory instead