Force a single checkpoint of the log (regardless of whether or not
there has been activity since the last checkpoint), and then exit.
</p>
<p>
When the <spanclass="bold"><strong>-1</strong></span> flag is specified, the
<spanclass="command"><strong>db_checkpoint</strong></span> 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.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-h</strong></span>
</p>
<p>
Specify a home directory for the database environment; by default, the
current working directory is used.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-k</strong></span>
</p>
<p>
Checkpoint the database at least as often as every <spanclass="bold"><strong>kbytes</strong></span> of log file are written.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-L</strong></span>
</p>
<p>
Log the execution of the <spanclass="command"><strong>db_checkpoint</strong></span> utility to the specified file
in the following format, where <spanclass="emphasis"><em>###</em></span> is the process
ID, and the date is the time the utility was started.
</p>
<preclass="programlisting"> db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995 </pre>
<p>
This file will be removed if the <spanclass="command"><strong>db_checkpoint</strong></span>
utility exits gracefully.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-P</strong></span>
</p>
<p>
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.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-p</strong></span>
</p>
<p>
Checkpoint the database at least every <spanclass="bold"><strong>min</strong></span> minutes
if there has been any activity since the last checkpoint.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-V</strong></span>
</p>
<p>
Write the library version number to the standard output, and exit.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-v</strong></span>
</p>
<p>
Write the time of each checkpoint attempt to the standard output.
</p>
</li>
</ul>
</div>
<p>
At least one of the <spanclass="bold"><strong>-1</strong></span>, <spanclass="bold"><strong>-k</strong></span>, and <spanclass="bold"><strong>-p</strong></span>
options must be specified.
</p>
<p>
The <spanclass="command"><strong>db_checkpoint</strong></span> utility uses a Berkeley DB
environment (as described for the <spanclass="bold"><strong>-h</strong></span>
option, the environment variable
<spanclass="bold"><strong>DB_HOME</strong></span>, 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, <spanclass="command"><strong>db_checkpoint</strong></span> should always be given the chance to detach
from the environment and exit gracefully. To cause <spanclass="command"><strong>db_checkpoint</strong></span> to
release all environment resources and exit cleanly, send it an
interrupt signal (SIGINT).
</p>
<p>
The <spanclass="command"><strong>db_checkpoint</strong></span> 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 <spanclass="command"><strong>db_checkpoint</strong></span> utility should be started.
</p>
<p>
The <spanclass="command"><strong>db_checkpoint</strong></span> utility exits 0 on success, and >0 if an error
