1.Dd December 3, 2003       \" DATE 
2.Dt db_printlog 1       \" Program name and manual section number 
3.Os Darwin
4.Sh NAME                 \" Section Header - required - don't modify 
5.Nm db_printlog
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 NrV
12.Op Fl h Ar home
13.Op Fl P Ar password
14.Sh DESCRIPTION          \" Section Header - required - don't modify
15The
16.Nm
17utility is a debugging utility that dumps Berkeley DB log files in a human-readable format.
18.Pp
19The options are as follows:
20.Bl -tag -width
21.It Fl h
22Specify a home directory for the database environment; by default, the current working directory is used.
23.It Fl N
24Do 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.
25.It Fl P
26Specify 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.
27.It Fl r
28Read the log files in reverse order.
29.It Fl V
30Write the library version number to the standard output, and exit.
31.El
32.Pp
33For more information on the
34.Nm
35output and using it to debug applications, see Reviewing Berkeley DB log files.
36.Pp
37The
38.Nm
39utility uses 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,
40.Nm
41should always be given the chance to detach from the environment and exit gracefully. To cause
42.Nm
43to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT).
44.Pp
45The 
46.Nm
47utility exits 0 on success, and >0 if an error occurs.
48.Pp
49.Sh ENVIRONMENT      \" May not be needed
50.Bl -tag -width "DB_HOME" \" ENV_VAR_1 is width of the string ENV_VAR_1
51.It Ev DB_HOME
52If 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.
53.El                      
54.\" .Sh FILES                \" File used or created by the topic of the man page
55.\" .Bl -tag -width "/Users/joeuser/Library/really_long_file_name" -compact
56.\" .It Pa /usr/share/file_name
57.\" FILE_1description
58.\" .It Pa /Users/joeuser/Library/really_long_file_name
59.\" FILE_2 description
60.\" .Sh DIAGNOSTICS       \" May not be needed
61.\" .Bl -diag
62.\" .It Diagnostic Tag
63.\" Diagnostic informtion here.
64.\" .It Diagnostic Tag
65.\" Diagnostic informtion here.
66.\" .El
67.Sh SEE ALSO 
68.Xr db_archive 1 ,
69.Xr db_checkpoint 1 ,
70.Xr db_deadlock 1 ,
71.Xr db_dump 1 ,
72.Xr db_load 1 ,
73.Xr db_recover 1 ,
74.Xr db_stat 1 ,
75.Xr db_upgrade 1 ,
76.Xr db_verify 1
77.\" .Sh BUGS              \" Document known, unremedied bugs 
78.\" .Sh HISTORY           \" Document history if command behaves in a unique manner 
79