db_printlog(1)

1DB_PRINTLOG(1)               BerkeleyDB Utilities               DB_PRINTLOG(1)
2
3
4

NAME

6       db_printlog - Dumps log files into a human-readable format
7

SYNOPSIS

9       db_printlog [-NrV] [-b start-LSN] [-e stop-LSN] [-h home] [-P password]
10       [-D bytes]
11

DESCRIPTION

13       The db_printlog utility is a debugging utility that dumps  Berkeley  DB
14       log files in a human-readable format.
15

OPTIONS

17       -b start-LSN
18              Display log records starting at log sequence number (LSN) start-
19              LSN; start-LSN is specified as a  file  number,  followed  by  a
20              slash  (/)  character,  followed  by  an  offset number, with no
21              intervening whitespace.
22
23       -D bytes
24              Specifies the maximum number of bytes to dump for each  key/data
25              item found in the specified database.  This option is only valid
26              when -da is also specified. This option overrides the value  set
27              for the "set_data_len" parameter in your DB_CONFIG file, if any.
28
29       -e stop-LSN
30              Stop  displaying  log records at log sequence number (LSN) stop-
31              LSN; stop-LSN is specified as a file number, followed by a slash
32              (/) character, followed by an offset number, with no intervening
33              whitespace.
34
35       -h home
36              Specify a  home  directory  for  the  database  environment;  by
37              default, the current working directory is used.
38
39       -N     Do not acquire shared region mutexes while running.  Other prob‐
40              lems, such as potentially fatal errors in Berkeley DB,  will  be
41              ignored  as  well.   This  option is intended only for debugging
42              errors, and should not be used under any other circumstances.
43
44       -P password
45              Specify an environment password.  Although Berkeley DB utilities
46              overwrite  password  strings as soon as possible, be aware there
47              may be a window of vulnerability on systems  where  unprivileged
48              users  can see command-line arguments or where utilities are not
49              able to overwrite the memory containing the  command-line  argu‐
50              ments.
51
52       -r     Read the log files in reverse order.
53
54       -V     Write  the  library  version  number to the standard output, and
55              exit.
56
57       The db_printlog utility uses a Berkeley DB  environment  (as  described
58       for  the  -h  option,  the environment variable DB_HOME, or because the
59       utility was run in a directory containing a Berkeley  DB  environment).
60       In order to avoid environment corruption when using a Berkeley DB envi‐
61       ronment, db_printlog should always be given the chance to  detach  from
62       the  environment  and exit gracefully.  To cause db_printlog to release
63       all environment resources and exit cleanly, send it an interrupt signal
64       (SIGINT).
65

EXIT STATUS

67       The db_printlog utility exits 0 on success, and >0 if an error occurs.
68

ENVIRONMENT

70       DB_HOME
71              If  the  -h option is not specified and the environment variable
72              DB_HOME is set, it is used as the path of the database home,  as
73              described in DB_ENV->open.
74

NOTES

76       If  the  application(s)  that  use  the  environment  make  use  of the
77       DB_ENV->set_lg_dir method, then in order for this utility to  run  cor‐
78       rectly, you need a DB_CONFIG file which sets the proper paths using the
79       set_lg_dir configuration parameter.
80