2
<!--Copyright 1997-2002 by Sleepycat Software, Inc.-->
3
<!--All rights reserved.-->
4
<!--See the file LICENSE for redistribution information.-->
7
<title>Berkeley DB: db_printlog</title>
8
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
9
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
12
<a name="2"><!--meow--></a>
13
<table width="100%"><tr valign=top>
18
<a href="../api_c/c_index.html"><img src="../images/api.gif" alt="API"></a><a href="../reftoc.html"><img src="../images/ref.gif" alt="Ref"></a>
22
<h3><pre>db_printlog [<b>-NrV</b>] [<b>-h home</b>] [<b>-P password</b>]</pre></h3>
24
<a name="3"><!--meow--></a>
25
<p>The db_printlog utility is a debugging utility that dumps Berkeley DB
26
log files in a human-readable format.
27
<p>The options are as follows:
29
<p><dt><b>-h</b><dd>Specify a home directory for the database environment; by
30
default, the current working directory is used.
31
<p><dt><b>-N</b><dd>Do not acquire shared region mutexes while running. Other problems,
32
such as potentially fatal errors in Berkeley DB, will be ignored as well.
33
This option is intended only for debugging errors, and should not be
34
used under any other circumstances.
35
<p><dt><b>-P</b><dd>Specify an environment password. Although Berkeley DB utilities overwrite
36
password strings as soon as possible, be aware there may be a window of
37
vulnerability on systems where unprivileged users can see command-line
38
arguments or where utilities are not able to overwrite the memory
39
containing the command-line arguments.
40
<p><dt><b>-r</b><dd>Read the log files in reverse order.
41
<p><dt><b>-V</b><dd>Write the library version number to the standard output, and exit.
43
<p>For more information on the db_printlog output and using it to
44
debug applications, see <a href="../ref/debug/printlog.html">Reviewing
45
Berkeley DB log files</a>.
46
<p>The db_printlog utility uses a Berkeley DB environment (as described for the
47
<b>-h</b> option, the environment variable <b>DB_HOME</b>, or
48
because the utility was run in a directory containing a Berkeley DB
49
environment). In order to avoid environment corruption when using a
50
Berkeley DB environment, db_printlog should always be given the chance to
51
detach from the environment and exit gracefully. To cause db_printlog
52
to release all environment resources and exit cleanly, send it an
53
interrupt signal (SIGINT).
54
<p>The db_printlog utility exits 0 on success, and >0 if an error occurs.
55
<h1>Environment Variables</h1>
57
<p><dt>DB_HOME<dd>If the <b>-h</b> option is not specified and the environment variable
58
DB_HOME is set, it is used as the path of the database home, as described
59
in <a href="../api_c/env_open.html">DB_ENV->open</a>.
62
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>