1.Dd December 3, 2003       \" DATE 
2.Dt db_verify 1       \" Program name and manual section number 
3.Os Darwin
4.Sh NAME                 \" Section Header - required - don't modify 
5.Nm db_verify
6.\" The following lines are read in generating the apropos(man -k) database. Use only key
7.\" words here as the database is built based on the words here and in the .ND line. 
8.\" Use .Nm macro to designate other names for the documented program.
9.Sh SYNOPSIS             \" Section Header - required - don't modify
10.Nm
11.Op Fl NoqV
12.Op Fl h Ar home
13.Op Fl P Ar password
14file ...
15.Sh DESCRIPTION          \" Section Header - required - don't modify
16The
17.Nm
18utility verifies the structure of one or more files and the databases they contain.
19.Pp
20The options are as follows:
21.Bl -tag -width
22.It Fl h
23Specify a home directory for the database environment; by default, the current working directory is used.
24.It Fl o
25Skip the database checks for btree and duplicate sort order and for hashing.
26.Pp
27If the file being verified contains databases with non-default comparison or hashing configurations, calling the 
28.Nm
29utility without the -o flag will usually return failure. The -o flag causes
30.Nm
31to ignore database sort or hash ordering and allows
32.Nm
33to be used on these files. To fully verify these files, verify them explicitly using the DB->verify method, after configuring the correct comparison or hashing functions.
34.It Fl N
35Do 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.
36.It Fl P
37Specify 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.
38.It Fl q
39Suppress the printing of any error descriptions, simply exit success or failure.
40.It Fl V
41Write the library version number to the standard output, and exit.
42.El
43.Pp
44.Em The
45.Nm
46utility does not perform any locking, even in Berkeley DB environments that are configured with a locking subsystem. As such, it should only be used on files that are not being modified by another thread of control.
47.Pp
48The
49.Nm
50utility may be used with 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, 
51.Nm
52should always be given the chance to detach from the environment and exit gracefully. To cause 
53.Nm
54to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT).
55.Pp
56The 
57.Nm
58utility exits 0 on success, and >0 if an error occurs.
59.Pp
60.Sh ENVIRONMENT      \" May not be needed
61.Bl -tag -width "DB_HOME" \" ENV_VAR_1 is width of the string ENV_VAR_1
62.It Ev DB_HOME
63If 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 DB_ENV->open.
64.El                      
65.\" .Sh FILES                \" File used or created by the topic of the man page
66.\" .Bl -tag -width "/Users/joeuser/Library/really_long_file_name" -compact
67.\" .It Pa /usr/share/file_name
68.\" FILE_1description
69.\" .It Pa /Users/joeuser/Library/really_long_file_name
70.\" FILE_2 description
71.\" .Sh DIAGNOSTICS       \" May not be needed
72.\" .Bl -diag
73.\" .It Diagnostic Tag
74.\" Diagnostic informtion here.
75.\" .It Diagnostic Tag
76.\" Diagnostic informtion here.
77.\" .El
78.Sh SEE ALSO 
79.Xr db_archive 1 ,
80.Xr db_checkpoint 1 ,
81.Xr db_deadlock 1 ,
82.Xr db_dump 1 ,
83.Xr db_load 1 ,
84.Xr db_printlog 1 ,
85.Xr db_recover 1 ,
86.Xr db_stat 1 ,
87.Xr db_upgrade 1
88.\" .Sh BUGS              \" Document known, unremedied bugs 
89.\" .Sh HISTORY           \" Document history if command behaves in a unique manner 
90