Berkeley DB: db_checkpoint
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,b+tree,btr ee,hash,hashing,transaction,transactions,locking,logging,access method,access me thods,java,C,C++

# db_checkpoint

`

###

    db_checkpoint [-1v]
        [-h home] [-k kbytes] [-L file] [-p min]

# Description

The db_checkpoint utility is a daemon process that monitors the database log and periodically calls txn_checkpoint to checkpoint it.

The options are as follows:

-1
  Checkpoint the log once, and then exit.

-h
  Specify a home directory for the database.

-k
  Checkpoint the database at least as often as every kbytes of log file are written.

-L
  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.

-p
  Checkpoint the database at least every min minutes.

-v
  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 one or more of the Berkeley 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 db_checkpoint utility does not attempt to create the Berkeley DB shared memory regions if they do not already exist. The application which creates the region should be started first, and then, once the region is created, the db_checkpoint utility should be started.

The txn_checkpoint function is the underlying function used by the db_checkpoint utility. See the db_checkpoint utility source code for an example of using txn_checkpoint in a POSIX 1003.1 environment.

The db_checkpoint utility exits 0 on success, and >0 if an error occurs.

# Environment Variables

DB_HOME
  If the -h option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in db_appinit.

# See Also

db_archive, db_checkpoint, db_deadlock, db_dump, db_load, db_recover, and db_stat.`