Gecko [ 122.154.134.11 ]

Name	Size	Permission
berkeley_db_svc.html	3.22 KB	-rw-r--r--
db_archive.html	5.46 KB	-rw-r--r--
db_checkpoint.html	4.47 KB	-rw-r--r--
db_codegen.html	9.31 KB	-rw-r--r--
db_deadlock.html	4.48 KB	-rw-r--r--
db_dump.html	7.08 KB	-rw-r--r--
db_hotbackup.html	7.69 KB	-rw-r--r--
db_load.html	10.15 KB	-rw-r--r--
db_printlog.html	3.51 KB	-rw-r--r--
db_recover.html	5.17 KB	-rw-r--r--
db_stat.html	5.93 KB	-rw-r--r--
db_upgrade.html	4.74 KB	-rw-r--r--
db_verify.html	3.72 KB	-rw-r--r--
index.html	2.31 KB	-rw-r--r--

Code Editor : db_checkpoint.html

<html>
<head>
<title>Berkeley DB: db_checkpoint</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<table width="100%"><tr valign=top>
<td>
db_checkpoint
</td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>db_checkpoint [-1Vv] [-h home]
 [-k kbytes] [-L file] [-P password] [-p min]</pre>
Description
<a name="2"></a>
The db_checkpoint utility is a daemon process that monitors the
database log, and periodically calls <a href="../../db4-devel-4.7.25/api_c/txn_checkpoint.html">DB_ENV-&gt;txn_checkpoint</a> to checkpoint
it.
The options are as follows:
 
-1<ul compact><li>Force a single checkpoint of the log (regardless of whether or not there
has been activity since the last checkpoint), and then exit.

When the -1 flag is specified, the db_checkpoint
utility will checkpoint the log even if unable to find an existing
database environment. This functionality is useful when upgrading
database environments from one version of Berkeley DB to another.</ul>
-h<ul compact><li>Specify a home directory for the database environment; by
default, the current working directory is used.</ul>
-k<ul compact><li>Checkpoint the database at least as often as every kbytes of log
file are written.</ul>
-L<ul compact><li>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 was started.
<blockquote><pre>db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995</pre></blockquote>
This file will be removed if the db_checkpoint utility exits gracefully.</ul>
-P<ul compact><li>Specify an environment password. Although Berkeley DB utilities overwrite
password strings as soon as possible, be aware there may be a window of
vulnerability on systems where unprivileged users can see command-line
arguments or where utilities are not able to overwrite the memory
containing the command-line arguments.</ul>
-p<ul compact><li>Checkpoint the database at least every min minutes if there has
been any activity since the last checkpoint.</ul>
-V<ul compact><li>Write the library version number to the standard output, and exit.</ul>
-v<ul compact><li>Write the time of each checkpoint attempt to the standard output.</ul>
 
At least one of the -1, -k, and -p options
must be specified.
The db_checkpoint utility uses a Berkeley DB environment (as described for the
-h option, the environment variable DB_HOME, or
because the utility was run in a directory containing a Berkeley DB
environment). In order to avoid environment corruption when using a
Berkeley DB environment, db_checkpoint should always be given the chance to
detach from the environment and exit gracefully. To cause db_checkpoint
to release all environment resources and exit cleanly, 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
that creates the region should be started first, and once the region is
created, the db_checkpoint utility should be started.
The <a href="../../db4-devel-4.7.25/api_c/txn_checkpoint.html">DB_ENV-&gt;txn_checkpoint</a> method is the underlying method used by the db_checkpoint utility.
See the db_checkpoint utility source code for an example of using <a href="../../db4-devel-4.7.25/api_c/txn_checkpoint.html">DB_ENV-&gt;txn_checkpoint</a>
in a IEEE/ANSI Std 1003.1 (POSIX) environment.
The db_checkpoint utility exits 0 on success, and &gt;0 if an error occurs.
 Environment Variables
 
DB_HOME<ul compact><li>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 <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a>.</ul>
 
</tt>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

${this.title}

Code Editor : db_checkpoint.html