• Home
  • History
  • Annotate
  • Line#
  • Navigate
  • Raw
  • Download
  • only in /asuswrt-rt-n18u-9.0.0.4.380.2695/release/src-rt/router/db-4.8.30/docs/api_reference/C/
1<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4  <head>
5    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6    <title>db_verify</title>
7    <link rel="stylesheet" href="apiReference.css" type="text/css" />
8    <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
9    <link rel="start" href="index.html" title="Berkeley DB C API Reference" />
10    <link rel="up" href="utilities.html" title="Appendix��1.�� Berkeley DB Command Line Utilities" />
11    <link rel="prev" href="db_upgrade.html" title="db_upgrade" />
12    <link rel="next" href="historic.html" title="Appendix��2.�� Historic Interfaces" />
13  </head>
14  <body>
15    <div class="navheader">
16      <table width="100%" summary="Navigation header">
17        <tr>
18          <th colspan="3" align="center">db_verify</th>
19        </tr>
20        <tr>
21          <td width="20%" align="left"><a accesskey="p" href="db_upgrade.html">Prev</a>��</td>
22          <th width="60%" align="center">Appendix��1.��
23                Berkeley DB Command Line Utilities
24        </th>
25          <td width="20%" align="right">��<a accesskey="n" href="historic.html">Next</a></td>
26        </tr>
27      </table>
28      <hr />
29    </div>
30    <div class="sect1" lang="en" xml:lang="en">
31      <div class="titlepage">
32        <div>
33          <div>
34            <h2 class="title" style="clear: both"><a id="db_verify"></a>db_verify</h2>
35          </div>
36        </div>
37      </div>
38      <pre class="programlisting">db_verify [-NoqV] [-h home] [-P password] file ...  </pre>
39      <p>
40         The <span class="command"><strong>db_verify</strong></span> utility verifies the structure of one or more files and
41         the databases they contain.
42    </p>
43      <p>
44        The options are as follows:
45    </p>
46      <div class="itemizedlist">
47        <ul type="disc">
48          <li>
49            <p>
50              <span class="bold"><strong>-h</strong></span>
51            </p>
52            <p>
53                 Specify a home directory for the database environment; by default, the
54                 current working directory is used.
55            </p>
56          </li>
57          <li>
58            <p>
59                 <span class="bold"><strong>-o</strong></span>
60            </p>
61            <p>
62                 Skip the database checks for btree and duplicate sort order and for
63                 hashing.
64             </p>
65            <p>
66                 If the file being verified contains databases with non-default
67                 comparison or hashing configurations, calling the <span class="command"><strong>db_verify</strong></span> utility
68                 without the <span class="bold"><strong>-o</strong></span> flag will usually
69                 return failure.  The <span class="bold"><strong>-o</strong></span> flag causes
70                 <span class="command"><strong>db_verify</strong></span> to ignore database sort or hash ordering and allows
71                 <span class="command"><strong>db_verify</strong></span> to be used on these files. To fully verify these files,
72                 verify them explicitly using the <a class="xref" href="dbverify.html" title="DB-&gt;verify()">DB-&gt;verify()</a>
73                 method, after configuring the correct comparison or hashing functions.
74            </p>
75          </li>
76          <li>
77            <p>
78                 <span class="bold"><strong>-N</strong></span>
79            </p>
80            <p>
81                 Do not acquire shared region mutexes while running.  Other problems,
82                 such as potentially fatal errors in Berkeley DB, will be ignored as
83                 well. This option is intended only for debugging errors, and should
84                 not be used under any other circumstances.
85            </p>
86          </li>
87          <li>
88            <p>
89                 <span class="bold"><strong>-P</strong></span>
90            </p>
91            <p>
92                 Specify an environment password.  Although Berkeley DB utilities
93                 overwrite password strings as soon as possible, be aware there may be
94                 a window of vulnerability on systems where unprivileged users can see
95                 command-line arguments or where utilities are not able to overwrite
96                 the memory containing the command-line arguments.
97            </p>
98          </li>
99          <li>
100            <p>
101                 <span class="bold"><strong>-q</strong></span>
102            </p>
103            <p>
104                 Suppress the printing of any error descriptions, simply exit success
105                 or failure.
106            </p>
107          </li>
108          <li>
109            <p>
110                 <span class="bold"><strong>-V</strong></span>
111            </p>
112            <p>
113                 Write the library version number to the standard output, and exit.
114            </p>
115          </li>
116        </ul>
117      </div>
118      <p>
119         <span class="bold"><strong>The <span class="command"><strong>db_verify</strong></span> utility does not perform any
120         locking, even in Berkeley DB environments that are configured with a
121         locking subsystem.  As such, it should only be used on files that are
122         not being modified by another thread of control.</strong></span>
123    </p>
124      <p>
125         The <span class="command"><strong>db_verify</strong></span> utility may be used with a Berkeley DB environment (as
126         described for the <span class="bold"><strong>-h</strong></span> option, the
127         environment variable <span class="bold"><strong>DB_HOME</strong></span>, or
128         because the utility was run in a directory containing a Berkeley DB
129         environment).  In order to avoid environment corruption when using a
130         Berkeley DB environment, <span class="command"><strong>db_verify</strong></span> should always be given the chance
131         to detach from the environment and exit gracefully.  To cause
132         <span class="command"><strong>db_verify</strong></span> to release all environment resources and exit cleanly, send
133         it an interrupt signal (SIGINT).
134    </p>
135      <p>
136         The <span class="command"><strong>db_verify</strong></span> utility exits 0 on success, and &gt;0 if an error
137         occurs.
138    </p>
139      <div class="sect2" lang="en" xml:lang="en">
140        <div class="titlepage">
141          <div>
142            <div>
143              <h3 class="title"><a id="id1716524"></a>Environment Variables</h3>
144            </div>
145          </div>
146        </div>
147        <div class="sect3" lang="en" xml:lang="en">
148          <div class="titlepage">
149            <div>
150              <div>
151                <h4 class="title"><a id="id1717330"></a>DB_HOME</h4>
152              </div>
153            </div>
154          </div>
155          <p>
156                          If the <span class="bold"><strong>-h</strong></span> option is not specified and
157                          the environment variable DB_HOME is set, it is used as the path of the
158                          database home, as described in the
159                          <a class="xref" href="envopen.html" title="DB_ENV-&gt;open()">DB_ENV-&gt;open()</a>
160                          method.
161                     </p>
162        </div>
163      </div>
164    </div>
165    <div class="navfooter">
166      <hr />
167      <table width="100%" summary="Navigation footer">
168        <tr>
169          <td width="40%" align="left"><a accesskey="p" href="db_upgrade.html">Prev</a>��</td>
170          <td width="20%" align="center">
171            <a accesskey="u" href="utilities.html">Up</a>
172          </td>
173          <td width="40%" align="right">��<a accesskey="n" href="historic.html">Next</a></td>
174        </tr>
175        <tr>
176          <td width="40%" align="left" valign="top">db_upgrade��</td>
177          <td width="20%" align="center">
178            <a accesskey="h" href="index.html">Home</a>
179          </td>
180          <td width="40%" align="right" valign="top">��Appendix��2.��
181                Historic Interfaces
182        </td>
183        </tr>
184      </table>
185    </div>
186  </body>
187</html>
188