1DB_CHECKPOINT(1) BerkeleyDB Utilities DB_CHECKPOINT(1)
2
3
4
6 db_checkpoint - Periodically checkpoint transactions
7
9 db_checkpoint [-1Vv] [-h home] [-k kbytes] [-L file] [-P password] [-p
10 min]
11
13 The db_checkpoint utility is a daemon process that monitors the data‐
14 base log, and periodically calls DB_ENV->txn_checkpoint to checkpoint
15 it.
16
18 -1 Checkpoint the log once, regardless of whether or not there has
19 been activity since the last checkpoint and then exit.
20
21 -h home
22 Specify a home directory for the database environment; by
23 default, the current working directory is used.
24
25 -k kbytes
26 Checkpoint the database at least as often as every kbytes of log
27 file are written.
28
29 -L file
30 Log the execution of the db_checkpoint utility to the specified
31 file in the following format, where ### is the process ID, and
32 the date is the time the utility was started.
33
34 db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995
35
36 This file will be removed if the db_checkpoint utility exits
37 gracefully.
38
39 -P password
40 Specify an environment password. Although Berkeley DB utilities
41 overwrite password strings as soon as possible, be aware there
42 may be a window of vulnerability on systems where unprivileged
43 users can see command-line arguments or where utilities are not
44 able to overwrite the memory containing the command-line argu‐
45 ments.
46
47 -p min Checkpoint the database at least every min minutes if there has
48 been any activity since the last checkpoint.
49
50 -V Write the library version number to the standard output, and
51 exit.
52
53 -v Write the time of each checkpoint attempt to the standard out‐
54 put.
55
56 At least one of the -1, -k, and -p options must be specified.
57
58 The db_checkpoint utility uses a Berkeley DB environment (as described
59 for the -h option, the environment variable DB_HOME, or because the
60 utility was run in a directory containing a Berkeley DB environment).
61 In order to avoid environment corruption when using a Berkeley DB envi‐
62 ronment, db_checkpoint should always be given the chance to detach from
63 the environment and exit gracefully. To cause db_checkpoint to release
64 all environment resources and exit cleanly, send it an interrupt signal
65 (SIGINT).
66
67 The db_checkpoint utility does not attempt to create the Berkeley DB
68 shared memory regions if they do not already exist. The application
69 that creates the region should be started first, and once the region is
70 created, the db_checkpoint utility should be started.
71
72 The DB_ENV->txn_checkpoint method is the underlying method used by the
73 db_checkpoint utility. See the db_checkpoint utility source code for an
74 example of using DB_ENV->txn_checkpoint in a IEEE/ANSI Std 1003.1
75 (POSIX) environment.
76
78 The db_checkpoint utility exits 0 on success, and >0 if an error
79 occurs.
80
82 DB_HOME
83 If the -h option is not specified and the environment variable
84 DB_HOME is set, it is used as the path of the database home, as
85 described in DB_ENV->open.
86
88 db_archive(1) db_deadlock(1) db_dump(1) db_hotbackup(1) db_log_ver‐
89 ify(1) db_load(1) db_printlog(1) db_recover(1) db_replicate(1)
90 db_stat(1) db_tuner(1) db_upgrade(1) db_verify(1)
91
92
93
94BerkeleyDB 5.3.28 06 December 2016 DB_CHECKPOINT(1)