Display log records starting at log sequence number (LSN) <spanclass="bold"><strong>start-LSN</strong></span>; <spanclass="bold"><strong>start-LSN</strong></span> is specified as a file number,
followed by a slash (/) character, followed by an offset number, with
no intervening whitespace.
</p>
</li>
<li>
<p>
<spanclass="bold"><strong>-e</strong></span>
</p>
<p>
Stop displaying log records at log sequence number (LSN) <spanclass="bold"><strong>stop-LSN</strong></span>; <spanclass="bold"><strong>stop-LSN</strong></span> is specified as a file number,
followed by a slash (/) character, followed by an offset number, with
no intervening whitespace.
</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>-N</strong></span>
</p>
<p>
Do not acquire shared region mutexes while running. Other problems,
such as potentially fatal errors in Berkeley DB, will be ignored as
well. This option is intended only for debugging errors, and should
not be used under any other circumstances.
</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>-r</strong></span>
</p>
<p>
Read the log files in reverse order.
</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>
</ul>
</div>
<p>
For more information on the <spanclass="command"><strong>db_printlog</strong></span> output and using it to debug
applications, see
<ahref="../../installation/debug_printlog.html"class="olink">Reviewing Berkeley DB log files</a>.
</p>
<p>
The <spanclass="command"><strong>db_printlog</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_printlog</strong></span> should always be given the chance to detach
from the environment and exit gracefully. To cause <spanclass="command"><strong>db_printlog</strong></span> to
release all environment resources and exit cleanly, send it an
interrupt signal (SIGINT).
</p>
<p>
The <spanclass="command"><strong>db_printlog</strong></span> utility exits 0 on success, and >0 if an error
