The db_checkpoint utility is a daemon process that monitors the database log and periodically calls txn_checkpoint(3) to checkpoint it.
The options are as follows:
Checkpoint the log once, and then exit.
Specify a home directory for the database.
Checkpoint the database at least as often as every kbytes of log file are written.
Log the execution of the db_checkpoint utility to the specified file in the following format, where ``###'' is the process ID, and the date is the time the utility starting running.
db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995
This file will be removed if the db_checkpoint utility exits gracefully.
Checkpoint the database at least every min minutes.
Write the time of each checkpoint to the standard output.
At least one of the -1, -k and -p options must be specified.
The db_checkpoint utility attaches to DB shared memory regions. In order to avoid region corruption, it should always be given the chance to detach and exit gracefully. To cause db_checkpoint to clean up after itself and exit, send it an interrupt signal (SIGINT).
The following environment variables affect the execution of db_checkpoint:
The DB library is a family of groups of functions that provides a modular programming interface to transactions and record-oriented file access. The library includes support for transactions, locking, logging and file page caching, as well as various indexed access methods. Many of the functional groups (e.g., the file page caching functions) are useful independent of the other DB functions, although some functional groups are explicitly based on other functional groups (e.g., transactions and logging).
lib/main.php:944: Notice: PageInfo: Cannot find action page