From 98380d9740a7b6d6027431f8753b2d62575c683c Mon Sep 17 00:00:00 2001
From: Ryan Tandy <ryan@nardis.ca>
Date: Mon, 17 Mar 2014 16:08:38 -0700
Subject: [PATCH] update manpages for db5.3

---
 .../{berkeley_db5.2_svc.1 => berkeley_db5.3_svc.1} | 16 +++++-----
 .../manpages/{db5.2_archive.1 => db5.3_archive.1}  | 28 +++++++++---------
 .../{db5.2_checkpoint.1 => db5.3_checkpoint.1}     | 26 ++++++++---------
 .../manpages/{db5.2_codegen.1 => db5.3_codegen.1}  |  4 +--
 .../{db5.2_deadlock.1 => db5.3_deadlock.1}         | 26 ++++++++---------
 debian/manpages/{db5.2_dump.1 => db5.3_dump.1}     | 26 ++++++++---------
 .../{db5.2_hotbackup.1 => db5.3_hotbackup.1}       | 20 ++++++-------
 debian/manpages/{db5.2_load.1 => db5.3_load.1}     | 34 +++++++++++-----------
 .../{db5.2_printlog.1 => db5.3_printlog.1}         | 16 +++++-----
 .../manpages/{db5.2_recover.1 => db5.3_recover.1}  | 20 ++++++-------
 debian/manpages/{db5.2_stat.1 => db5.3_stat.1}     | 18 ++++++------
 .../manpages/{db5.2_upgrade.1 => db5.3_upgrade.1}  | 26 ++++++++---------
 debian/manpages/{db5.2_verify.1 => db5.3_verify.1} | 24 +++++++--------
 13 files changed, 142 insertions(+), 142 deletions(-)
 rename debian/manpages/{berkeley_db5.2_svc.1 => berkeley_db5.3_svc.1} (84%)
 rename debian/manpages/{db5.2_archive.1 => db5.3_archive.1} (83%)
 rename debian/manpages/{db5.2_checkpoint.1 => db5.3_checkpoint.1} (78%)
 rename debian/manpages/{db5.2_codegen.1 => db5.3_codegen.1} (99%)
 rename debian/manpages/{db5.2_deadlock.1 => db5.3_deadlock.1} (79%)
 rename debian/manpages/{db5.2_dump.1 => db5.3_dump.1} (86%)
 rename debian/manpages/{db5.2_hotbackup.1 => db5.3_hotbackup.1} (90%)
 rename debian/manpages/{db5.2_load.1 => db5.3_load.1} (89%)
 rename debian/manpages/{db5.2_printlog.1 => db5.3_printlog.1} (84%)
 rename debian/manpages/{db5.2_recover.1 => db5.3_recover.1} (85%)
 rename debian/manpages/{db5.2_stat.1 => db5.3_stat.1} (91%)
 rename debian/manpages/{db5.2_upgrade.1 => db5.3_upgrade.1} (82%)
 rename debian/manpages/{db5.2_verify.1 => db5.3_verify.1} (78%)

diff --git a/debian/manpages/berkeley_db5.2_svc.1 b/debian/manpages/berkeley_db5.3_svc.1
similarity index 84%
rename from debian/manpages/berkeley_db5.2_svc.1
rename to debian/manpages/berkeley_db5.3_svc.1
index b1d45bb..5cee68a 100644
--- a/debian/manpages/berkeley_db5.2_svc.1
+++ b/debian/manpages/berkeley_db5.3_svc.1
@@ -1,13 +1,13 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH BERKELEY_DB5.2_SVC 1 "28 January 2005"
+.TH BERKELEY_DB5.3_SVC 1 "28 January 2005"
 .SH NAME
-berkeley_db5.2_svc \- Berkeley DB RPC server
+berkeley_db5.3_svc \- Berkeley DB RPC server
 .SH SYNOPSIS
-.B berkeley_db5.2_svc
+.B berkeley_db5.3_svc
 [-Vv] [-h home] [-I seconds] [-L file] [-t seconds] [-T seconds]
 .SH DESCRIPTION
-The berkeley_db5.2_svc utility is the Berkeley DB RPC server.
+The berkeley_db5.3_svc utility is the Berkeley DB RPC server.
 .SH OPTIONS
 .IP \fB\-h\fR
 Add the specified home directory to the list of allowed home directories
@@ -24,13 +24,13 @@ must always be single-threaded.
 Set the default idle timeout for client environments to the specified
 number of seconds.  The default timeout is 24 hours.
 .IP \fB\-L\fR
-Log the execution of the berkeley_db5.2_svc utility to the specified file in the
+Log the execution of the berkeley_db5.3_svc utility to the specified file in the
 following format, where \fI###\fR is the process ID, and the date
 is the time the utility was started.
 .sp
-berkeley_db5.2_svc: ### Wed Jun 15 01:23:45 EDT 1995
+berkeley_db5.3_svc: ### Wed Jun 15 01:23:45 EDT 1995
 .sp
-This file will be removed if the berkeley_db5.2_svc utility exits gracefully.
+This file will be removed if the berkeley_db5.3_svc utility exits gracefully.
 .IP \fB\-t\fR
 Set the default timeout for client resources (idle transactions and
 cursors) to the specified number of seconds.  When the timeout expires,
@@ -46,7 +46,7 @@ Write the library version number to the standard output, and exit.
 .IP \fB\-v\fR
 Run in verbose mode.
 .PP
-The berkeley_db5.2_svc utility exits 0 on success, and >0 if an error occurs.
+The berkeley_db5.3_svc utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
diff --git a/debian/manpages/db5.2_archive.1 b/debian/manpages/db5.3_archive.1
similarity index 83%
rename from debian/manpages/db5.2_archive.1
rename to debian/manpages/db5.3_archive.1
index 41a62b4..ca6e6be 100644
--- a/debian/manpages/db5.2_archive.1
+++ b/debian/manpages/db5.3_archive.1
@@ -1,13 +1,13 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_ARCHIVE 1 "28 January 2005"
+.TH DB5.3_ARCHIVE 1 "28 January 2005"
 .SH NAME
-db5.2_archive \- Find unused log files for archiving purposes
+db5.3_archive \- Find unused log files for archiving purposes
 .SH SYNOPSIS
-.B db5.2_archive
+.B db5.3_archive
 [-adlsVv] [-h home] [-P password]
 .SH DESCRIPTION
-The db5.2_archive utility writes the pathnames of log files that
+The db5.3_archive utility writes the pathnames of log files that
 are no longer in use (for example, no longer involved in active
 transactions), to the standard output, one pathname per line.  These
 log files should be written to backup media to provide for recovery in
@@ -39,12 +39,12 @@ containing the command-line arguments.
 Write the pathnames of all the database files that need to be archived
 in order to recover the database from catastrophic failure.  If any of
 the database files have not been accessed during the lifetime of the
-current log files, db5.2_archive will not include them in this
+current log files, db5.3_archive will not include them in this
 output.
 .sp
 It is possible that some of the files to which the log refers have since
-been deleted from the system.  In this case, db5.2_archive will
-ignore them.  When db5.2_recover is run, any files to which the
+been deleted from the system.  In this case, db5.3_archive will
+ignore them.  When db5.3_recover is run, any files to which the
 log refers that are not present during recovery are assumed to have been
 deleted and will not be recovered.
 .IP \fB\-V\fR
@@ -61,7 +61,7 @@ and have open file descriptors for log files as well.  On operating
 systems where filesystem related system calls (for example, rename and
 unlink on Windows/NT) can fail if a process has an open file descriptor
 for the affected file, attempting to move or remove the log files listed
-by db5.2_archive may fail.  All Berkeley DB internal use of log cursors
+by db5.3_archive may fail.  All Berkeley DB internal use of log cursors
 operates on active log files only and furthermore, is short-lived in
 nature.  So, an application seeing such a failure should be restructured
 to close any open log cursors it may have, and otherwise to retry the
@@ -69,20 +69,20 @@ operation until it succeeds.  (Although the latter is not likely to be
 necessary; it is hard to imagine a reason to move or rename a log file
 in which transactions are being logged or aborted.)
 .PP
-The db5.2_archive utility uses a Berkeley DB environment (as described for the
+The db5.3_archive utility uses a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_archive should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_archive
+Berkeley DB environment, db5.3_archive should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_archive
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The DB_ENV->log_archive method is the underlying method used by the db5.2_archive utility.
-See the db5.2_archive utility source code for an example of using
+The DB_ENV->log_archive method is the underlying method used by the db5.3_archive utility.
+See the db5.3_archive utility source code for an example of using
 DB_ENV->log_archive in a IEEE/ANSI Std 1003.1 (POSIX) environment.
 .PP
-The db5.2_archive utility exits 0 on success, and >0 if an error occurs.
+The db5.3_archive utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
diff --git a/debian/manpages/db5.2_checkpoint.1 b/debian/manpages/db5.3_checkpoint.1
similarity index 78%
rename from debian/manpages/db5.2_checkpoint.1
rename to debian/manpages/db5.3_checkpoint.1
index 15e827b..58b126c 100644
--- a/debian/manpages/db5.2_checkpoint.1
+++ b/debian/manpages/db5.3_checkpoint.1
@@ -1,13 +1,13 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_CHECKPOINT 1 "28 January 2005"
+.TH DB5.3_CHECKPOINT 1 "28 January 2005"
 .SH NAME
-db5.2_checkpoint \- Periodically checkpoint transactions
+db5.3_checkpoint \- Periodically checkpoint transactions
 .SH SYNOPSIS
-.B db5.2_checkpoint
+.B db5.3_checkpoint
 [-1Vv] [-h home] [-k kbytes] [-L file] [-P password] [-p min]
 .SH DESCRIPTION
-The db5.2_checkpoint utility is a daemon process that monitors the database log,
+The db5.3_checkpoint utility is a daemon process that monitors the database log,
 and periodically calls DB_ENV->txn_checkpoint to checkpoint it.
 .SH OPTIONS
 .IP \fB\-1\fR
@@ -20,14 +20,14 @@ default, the current working directory is used.
 Checkpoint the database at least as often as every \fBkbytes\fR of log
 file are written.
 .IP \fB\-L\fR
-Log the execution of the db5.2_checkpoint utility to the specified file in the
+Log the execution of the db5.3_checkpoint utility to the specified file in the
 following format, where \fI###\fR is the process ID, and the date
 is the time the utility was started.
 .sp
 .TP 8
 db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995
 .sp
-This file will be removed if the db5.2_checkpoint utility exits gracefully.
+This file will be removed if the db5.3_checkpoint utility exits gracefully.
 .IP \fB\-P\fR
 Specify an environment password.  Although Berkeley DB utilities overwrite
 password strings as soon as possible, be aware there may be a window of
@@ -45,26 +45,26 @@ Write the time of each checkpoint attempt to the standard output.
 At least one of the \fB-1\fR, \fB-k\fR, and \fB-p\fR options
 must be specified.
 .PP
-The db5.2_checkpoint utility uses a Berkeley DB environment (as described for the
+The db5.3_checkpoint utility uses a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_checkpoint should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_checkpoint
+Berkeley DB environment, db5.3_checkpoint should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_checkpoint
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_checkpoint utility does not attempt to create the Berkeley DB
+The db5.3_checkpoint utility does not attempt to create the Berkeley DB
 shared memory regions if they do not already exist.  The application
 that creates the region should be started first, and once the region is
-created, the db5.2_checkpoint utility should be started.
+created, the db5.3_checkpoint utility should be started.
 .PP
 The DB_ENV->txn_checkpoint method is the underlying method used by the
-db5.2_checkpoint utility. See the db_checkpoint utility source code for an
+db5.3_checkpoint utility. See the db_checkpoint utility source code for an
 example of using DB_ENV->txn_checkpoint in a IEEE/ANSI Std 1003.1
 (POSIX) environment.
 .PP
-The db5.2_checkpoint utility exits 0 on success, and >0 if an error occurs.
+The db5.3_checkpoint utility exits 0 on success, and >0 if an error occurs.
 .PP
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
diff --git a/debian/manpages/db5.2_codegen.1 b/debian/manpages/db5.3_codegen.1
similarity index 99%
rename from debian/manpages/db5.2_codegen.1
rename to debian/manpages/db5.3_codegen.1
index 5e533a1..cb0e7bd 100644
--- a/debian/manpages/db5.2_codegen.1
+++ b/debian/manpages/db5.3_codegen.1
@@ -4,10 +4,10 @@
 .\" <!--See the file LICENSE for redistribution information.-->
 .\"
 .Dd January 12, 2011
-.Dt DB5.2_CODEGEN 1
+.Dt DB5.3_CODEGEN 1
 .Os "Berkeley DB"
 .Sh NAME
-.Nm db5.2_codegen
+.Nm db5.3_codegen
 .Nd generate application code for Berkeley DB
 .Sh SYNOPSIS
 .Nm
diff --git a/debian/manpages/db5.2_deadlock.1 b/debian/manpages/db5.3_deadlock.1
similarity index 79%
rename from debian/manpages/db5.2_deadlock.1
rename to debian/manpages/db5.3_deadlock.1
index 0ff6035..27b162b 100644
--- a/debian/manpages/db5.2_deadlock.1
+++ b/debian/manpages/db5.3_deadlock.1
@@ -1,13 +1,13 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_DEADLOCK 1 "28 January 2005"
+.TH DB5.3_DEADLOCK 1 "28 January 2005"
 .SH NAME
-db5.2_deadlock \- Detect and abort deadlocks
+db5.3_deadlock \- Detect and abort deadlocks
 .SH SYNOPSIS
-.B db5.2_deadlock
+.B db5.3_deadlock
 [-Vv] [-a e | m | n | o | W | w | y] [-h home] [-L file] [-t sec.usec]
 .SH DESCRIPTION
-The db5.2_deadlock utility traverses the database environment lock region, and
+The db5.3_deadlock utility traverses the database environment lock region, and
 aborts a lock request each time it detects a deadlock or a lock request that
 has timed out. By default, in the case of a deadlock, a random lock request is
 chosen to be aborted.
@@ -43,14 +43,14 @@ abort any lock request that has timed out
 Specify a home directory for the database environment; by
 default, the current working directory is used.
 .IP \fB\-L\fR
-Log the execution of the db5.2_deadlock utility to the specified file in the
+Log the execution of the db5.3_deadlock utility to the specified file in the
 following format, where \fI###\fR is the process ID, and the date
 is the time the utility was started.
 .sp
 .TP 8
 db_deadlock: ### Wed Jun 15 01:23:45 EDT 1995
 .sp
-This file will be removed if the db5.2_deadlock utility exits gracefully.
+This file will be removed if the db5.3_deadlock utility exits gracefully.
 .IP \fB\-t\fR
 Check the database environment every \fBsec\fR seconds plus
 \fBusec\fR microseconds to see if a process has been forced to wait
@@ -61,29 +61,29 @@ Write the library version number to the standard output, and exit.
 .IP \fB\-v\fR
 Run in verbose mode, generating messages each time the detector runs.
 .PP
-If the \fB-t\fR option is not specified, db5.2_deadlock will
+If the \fB-t\fR option is not specified, db5.3_deadlock will
 run once and exit.
 .PP
-The db5.2_deadlock utility uses a Berkeley DB environment (as described for the
+The db5.3_deadlock utility uses a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_deadlock should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_deadlock
+Berkeley DB environment, db5.3_deadlock should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_deadlock
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_deadlock utility does not attempt to create the Berkeley DB
+The db5.3_deadlock utility does not attempt to create the Berkeley DB
 shared memory regions if they do not already exist.  The application
 which creates the region should be started first, and then, once the
-region is created, the db5.2_deadlock utility should be started.
+region is created, the db5.3_deadlock utility should be started.
 .PP
 The DB_ENV->lock_detect method is the underlying method used by the
 db_deadlock utility. See the db_deadlock utility source code for an
 example of using DB_ENV->lock_detect
 in a IEEE/ANSI Std 1003.1 (POSIX) environment.
 .PP
-The db5.2_deadlock utility exits 0 on success, and >0 if an error occurs.
+The db5.3_deadlock utility exits 0 on success, and >0 if an error occurs.
 .PP
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
diff --git a/debian/manpages/db5.2_dump.1 b/debian/manpages/db5.3_dump.1
similarity index 86%
rename from debian/manpages/db5.2_dump.1
rename to debian/manpages/db5.3_dump.1
index 3bb8683..400c4fa 100644
--- a/debian/manpages/db5.2_dump.1
+++ b/debian/manpages/db5.3_dump.1
@@ -1,14 +1,14 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_DUMP 1 "28 January 2005"
+.TH DB5.3_DUMP 1 "28 January 2005"
 .SH NAME
-db5.2_dump \- Write database to flat-text format
+db5.3_dump \- Write database to flat-text format
 .SH SYNOPSIS
-.B db5.2_dump
+.B db5.3_dump
 [-klNpRrV] [-d ahr] [-f output] [-h home] [-P password] [-s database] file
 .SH DESCRIPTION
-The db5.2_dump utility reads the database file file and writes it to the standard
-output using a portable flat-text format understood by the db5.2_load utility.
+The db5.3_dump utility reads the database file file and writes it to the standard
+output using a portable flat-text format understood by the db5.3_load utility.
 The file argument must be a file produced using the Berkeley DB library
 functions.
 .SH OPTIONS
@@ -85,29 +85,29 @@ prefix and comparison functions.
 beyond repair permitting neither record storage or retrieval.\fR
 .PP
 The only available workaround for either case is to modify the sources
-for the db5.2_load utility to load the database using the correct
+for the db5.3_load utility to load the database using the correct
 hash, prefix, and comparison functions.
 .PP
-The db5.2_dump utility output format is documented in the
+The db5.3_dump utility output format is documented in the
 Dump Output Formats section of the Berkeley DB Reference Guide.
 .PP
-The db5.2_dump utility may be used with a Berkeley DB environment (as described for the
+The db5.3_dump utility may be used with a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_dump should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_dump
+Berkeley DB environment, db5.3_dump should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_dump
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-Even when using a Berkeley DB database environment, the db5.2_dump
+Even when using a Berkeley DB database environment, the db5.3_dump
 utility does not use any kind of database locking if it is invoked with
 the \fB-d\fR, \fB-R\fR, or \fB-r\fR arguments.   If used with
-one of these arguments, the db5.2_dump utility may only be safely
+one of these arguments, the db5.3_dump utility may only be safely
 run on databases that are not being modified by any other process;
 otherwise, the output may be corrupt.
 .PP
-The db5.2_dump utility exits 0 on success, and >0 if an error occurs.
+The db5.3_dump utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
diff --git a/debian/manpages/db5.2_hotbackup.1 b/debian/manpages/db5.3_hotbackup.1
similarity index 90%
rename from debian/manpages/db5.2_hotbackup.1
rename to debian/manpages/db5.3_hotbackup.1
index 1b409de..7e2d71d 100644
--- a/debian/manpages/db5.2_hotbackup.1
+++ b/debian/manpages/db5.3_hotbackup.1
@@ -1,15 +1,15 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_HOTBACKUP 1 "28 January 2005"
+.TH DB5.3_HOTBACKUP 1 "28 January 2005"
 .SH NAME
-db5.2_hotbackup \- Create "hot backup" or "hot failover" snapshots
+db5.3_hotbackup \- Create "hot backup" or "hot failover" snapshots
 .SH SYNOPSIS
-.B db5.2_hotbackup
+.B db5.3_hotbackup
 [-cDuVv] [-d data_dir ...] [-h home] [-l log_dir] [-P password] -b backup_dir
 .SH DESCRIPTION
-The db5.2_hotbackup utility creates "hot backup" or "hot failover" snapshots of Berkeley DB database environments.
+The db5.3_hotbackup utility creates "hot backup" or "hot failover" snapshots of Berkeley DB database environments.
 .PP
-The db5.2_hotbackup utility performs the following steps:
+The db5.3_hotbackup utility performs the following steps:
 .RS
 .IP 1.
 If the \-c option is specified, checkpoint the source home database
@@ -35,7 +35,7 @@ Perform catastrophic recovery on the hot backup.
 Remove any unnecessary log files from the hot backup. 
 .RE
 .PP
-The db5.2_hotbackup utility does not resolve pending transactions that are in the
+The db5.3_hotbackup utility does not resolve pending transactions that are in the
 prepared state. Applications that use DB_TXN->prepare should specify
 DB_RECOVER_FATAL when opening the environment, and run DB_ENV->txn_recover to
 resolve any pending transactions, when failing over to the hot backup.
@@ -97,16 +97,16 @@ or the log directory in this mode, as the DB_CONFIG configuration
 file copied into the target directory would then point at the source
 directories and running recovery would corrupt the source data files.\fR
 .PP
-The db5.2_hotbackup utility uses a Berkeley DB environment (as described for the
+The db5.3_hotbackup utility uses a Berkeley DB environment (as described for the
 \fB\-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_hotbackup should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_hotbackup
+Berkeley DB environment, db5.3_hotbackup should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_hotbackup
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_hotbackup utility exits 0 on success, and >0 if an error occurs.
+The db5.3_hotbackup utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
diff --git a/debian/manpages/db5.2_load.1 b/debian/manpages/db5.3_load.1
similarity index 89%
rename from debian/manpages/db5.2_load.1
rename to debian/manpages/db5.3_load.1
index 22c1fec..3f825c8 100644
--- a/debian/manpages/db5.2_load.1
+++ b/debian/manpages/db5.3_load.1
@@ -1,19 +1,19 @@
 .\" Manual Page for Berkeley DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_LOAD 1 "22 November 2009"
+.TH DB5.3_LOAD 1 "22 November 2009"
 .SH NAME
-db5.2_load \- Load data from standard input
+db5.3_load \- Load data from standard input
 .SH SYNOPSIS
-.B db5.2_load
+.B db5.3_load
 [-nTV] [-c name=value] [-f file] [-h home] [-P password] [-t btree | hash | queue | recno] file
 
-.B db5.2_load
+.B db5.3_load
 [-r lsn | fileid] [-h home] [-P password] file
 .SH DESCRIPTION
-The db5.2_load utility reads from the standard input and loads it into the
+The db5.3_load utility reads from the standard input and loads it into the
 database file. The database file is created if it does not already exist.
 .PP
-The input to db5.2_load must be in the output format specified by the db5.0_dump
+The input to db5.3_load must be in the output format specified by the db5.0_dump
 utility, utilities, or as specified for the -T below.
 .SH OPTIONS
 .IP \fB\-c\fR
@@ -29,7 +29,7 @@ Specify a home directory for the database environment.
 .sp
 If a home directory is specified, the database environment is opened
 using the DB_INIT_LOCK, DB_INIT_LOG, DB_INIT_MPOOL, DB_INIT_TXN, and
-DB_USE_ENVIRON flags to DB_ENV->open.  (This means that db5.2_load can be
+DB_USE_ENVIRON flags to DB_ENV->open.  (This means that db5.3_load can be
 used to load data into databases while they are in use by other
 processes.) If the DB_ENV->open call fails, or if no home
 directory is specified, the database is still updated, but the
@@ -88,7 +88,7 @@ as a hexadecimal specification of a single character; for example,
 .sp
 For this reason, any backslash or newline characters that naturally
 occur in the text input must be escaped to avoid misinterpretation by
-db5.2_load.
+db5.3_load.
 .sp
 If the \fB-T\fR option is specified, the underlying access method type
 must be specified using the \fB-t\fR option.
@@ -100,36 +100,36 @@ database was dumped.
 .sp
 Btree and Hash databases may be converted from one to the other.  Queue
 and Recno databases may be converted from one to the other.  If the
-\fB-k\fR option was specified on the call to db5.2_dump then Queue
+\fB-k\fR option was specified on the call to db5.3_dump then Queue
 and Recno databases may be converted to Btree or Hash, with the key being
 the integer record number.
 .IP \fB\-V\fR
 Write the library version number to the standard output, and exit.
 .PP
-The db5.2_load utility may be used with a Berkeley DB environment (as described for the
+The db5.3_load utility may be used with a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_load should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_load
+Berkeley DB environment, db5.3_load should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_load
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_load utility exits 0 on success, 1 if one or more key/data
+The db5.3_load utility exits 0 on success, 1 if one or more key/data
 pairs were not loaded into the database because the key already existed,
 and >1 if an error occurs.
 .SH EXAMPLES
-The db5.2_load utility can be used to load text files into databases.
+The db5.3_load utility can be used to load text files into databases.
 For example, the following command loads the standard UNIX
 \fI/etc/passwd\fR file into a database, with the login name as the
 key item and the entire password entry as the data item:
 .PP
 .TP 8
 awk \-F: '{print $1; print $0}' < /etc/passwd |
-sed 's/\\\\/\\\\\\\\/g' | db5.2_load \-T \-t hash passwd.db
+sed 's/\\\\/\\\\\\\\/g' | db5.3_load \-T \-t hash passwd.db
 .PP
 Note that backslash characters naturally occurring in the text are escaped
-to avoid interpretation as escape characters by db5.2_load.
+to avoid interpretation as escape characters by db5.3_load.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
@@ -137,7 +137,7 @@ DB_HOME is set, it is used as the path of the database home, as described
 in DB_ENV->open.
 .SH SUPPORTED KEYWORDS
 The following keywords are supported for the \fB-c\fR command-line
-ption to the db5.2_load utility.  See DB->open for further
+ption to the db5.3_load utility.  See DB->open for further
 discussion of these keywords and what values should be specified.
 .PP
 The parenthetical listing specifies how the value part of the
diff --git a/debian/manpages/db5.2_printlog.1 b/debian/manpages/db5.3_printlog.1
similarity index 84%
rename from debian/manpages/db5.2_printlog.1
rename to debian/manpages/db5.3_printlog.1
index 5f1fc22..34bfad2 100644
--- a/debian/manpages/db5.2_printlog.1
+++ b/debian/manpages/db5.3_printlog.1
@@ -1,13 +1,13 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_PRINTLOG 1 "28 January 2005"
+.TH DB5.3_PRINTLOG 1 "28 January 2005"
 .SH NAME
-db5.2_printlog \- Dumps Berkeley DB log files in a human-readable format
+db5.3_printlog \- Dumps Berkeley DB log files in a human-readable format
 .SH SYNOPSIS
-.B db5.2_printlog
+.B db5.3_printlog
 [-NrV] [-b start-LSN] [-e stop-LSN] [-h home] [-P password]
 .SH DESCRIPTION
-The db5.2_printlog utility is a debugging utility that dumps Berkeley DB log files
+The db5.3_printlog utility is a debugging utility that dumps Berkeley DB log files
 in a human-readable format.
 .SH OPTIONS
 .IP \fB\-b\fR
@@ -37,16 +37,16 @@ Read the log files in reverse order.
 .IP \fB\-V\fR
 Write the library version number to the standard output, and exit.
 .PP
-The db5.2_printlog utility uses a Berkeley DB environment (as described for the
+The db5.3_printlog utility uses a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_printlog should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_printlog
+Berkeley DB environment, db5.3_printlog should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_printlog
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_printlog utility exits 0 on success, and >0 if an error occurs.
+The db5.3_printlog utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
diff --git a/debian/manpages/db5.2_recover.1 b/debian/manpages/db5.3_recover.1
similarity index 85%
rename from debian/manpages/db5.2_recover.1
rename to debian/manpages/db5.3_recover.1
index d222f4d..f91992b 100644
--- a/debian/manpages/db5.2_recover.1
+++ b/debian/manpages/db5.3_recover.1
@@ -1,15 +1,15 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_RECOVER 1 "28 January 2005"
+.TH DB5.3_RECOVER 1 "28 January 2005"
 .SH NAME
-db5.2_recover \- Restore the database to a consistent state
+db5.3_recover \- Restore the database to a consistent state
 .SH SYNOPSIS
-.B db5.2_recover
+.B db5.3_recover
 [-ceVv] [-h home] [-P password] [-t [[CC]YY]MMDDhhmm[.SS]]]
 .SH DESCRIPTION
-The db5.2_recover utility must be run after an unexpected application, Berkeley
+The db5.3_recover utility must be run after an unexpected application, Berkeley
 DB, or system failure to restore the database to a consistent state. All
-committed transactions are guaranteed to appear after db5.2_recover has run, and
+committed transactions are guaranteed to appear after db5.3_recover has run, and
 all uncommitted transactions will be completely undone.
 .SH OPTIONS
 .IP \fB\-c\fR
@@ -69,20 +69,20 @@ links).
 If the failure was not catastrophic, the files present on the system at the
 time of failure are sufficient to perform recovery.
 .PP
-If log files are missing, db5.2_recover will identify the missing
+If log files are missing, db5.3_recover will identify the missing
 log file(s) and fail, in which case the missing log files need to be
 restored and recovery performed again.
 .PP
-The db5.2_recover utility uses a Berkeley DB environment (as described for the
+The db5.3_recover utility uses a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_recover should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_recover
+Berkeley DB environment, db5.3_recover should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_recover
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_recover utility exits 0 on success, and >0 if an error occurs.
+The db5.3_recover utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
diff --git a/debian/manpages/db5.2_stat.1 b/debian/manpages/db5.3_stat.1
similarity index 91%
rename from debian/manpages/db5.2_stat.1
rename to debian/manpages/db5.3_stat.1
index b6265bc..c204ce3 100644
--- a/debian/manpages/db5.2_stat.1
+++ b/debian/manpages/db5.3_stat.1
@@ -1,16 +1,16 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_STAT 1 "28 January 2005"
+.TH DB5.3_STAT 1 "28 January 2005"
 .SH NAME
-db5.2_stat \- Display statistics for Berkeley DB environments
+db5.3_stat \- Display statistics for Berkeley DB environments
 .SH SYNOPSIS
-.B db5.2_stat
+.B db5.3_stat
 -d file [-fN] [-h home] [-P password] [-s database]
 
-.B db5.2_stat
+.B db5.3_stat
 [-cEelmNrtVZ] [-C Aclop] [-h home] [-L A] [-M A] [-R A] [-P password]
 .SH DESCRIPTION
-The db5.2_stat utility displays statistics for Berkeley DB environments.
+The db5.3_stat utility displays statistics for Berkeley DB environments.
 .SH OPTIONS
 .IP \fB\-C\fR
 Display internal information about the locking subsystem.  (The output
@@ -105,16 +105,16 @@ combination of gigabytes (GB), megabytes (MB), kilobytes (KB), and bytes
 any special notation, and values larger than 10 million are displayed
 as a number followed by "M".
 .PP
-The db5.2_stat utility may be used with a Berkeley DB environment (as described for the
+The db5.3_stat utility may be used with a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_stat should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_stat
+Berkeley DB environment, db5.3_stat should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_stat
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_stat utility exits 0 on success, and >0 if an error occurs.
+The db5.3_stat utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
diff --git a/debian/manpages/db5.2_upgrade.1 b/debian/manpages/db5.3_upgrade.1
similarity index 82%
rename from debian/manpages/db5.2_upgrade.1
rename to debian/manpages/db5.3_upgrade.1
index 4433af0..827df60 100644
--- a/debian/manpages/db5.2_upgrade.1
+++ b/debian/manpages/db5.3_upgrade.1
@@ -1,13 +1,13 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_UPGRADE 1 "28 January 2005"
+.TH DB5.3_UPGRADE 1 "28 January 2005"
 .SH NAME
-db5.2_upgrade \- Upgrade the Berkeley DB version to the current release version.
+db5.3_upgrade \- Upgrade the Berkeley DB version to the current release version.
 .SH SYNOPSIS
-.B db5.2_upgrade
+.B db5.3_upgrade
 [-NsVv] [-h home] [-P password] file ...
 .SH DESCRIPTION
-The db5.2_upgrade utility upgrades the Berkeley DB version of one or more files
+The db5.3_upgrade utility upgrades the Berkeley DB version of one or more files
 and the databases they contain to the current release version.
 .SH OPTIONS
 .IP \fB\-h\fR
@@ -36,18 +36,18 @@ flag means that the duplicates are sorted; otherwise, they are assumed
 to be unsorted.  Incorrectly specifying the value of this flag may lead
 to database corruption.
 .sp
-Because the db5.2_upgrade utility upgrades a physical file
+Because the db5.3_upgrade utility upgrades a physical file
 (including all the databases it contains), it is not possible to use
-db5.2_upgrade to upgrade files where some of the databases it
+db5.3_upgrade to upgrade files where some of the databases it
 includes have sorted duplicate data items, and some of the databases it
 includes have unsorted duplicate data items. If the file does not have
 more than a single database, if the databases do not support duplicate
 data items, or if all the databases that support duplicate data items
 support the same style of duplicates (either sorted or unsorted),
-db5.2_upgrade will work correctly as long as the \fB-s\fR flag
+db5.3_upgrade will work correctly as long as the \fB-s\fR flag
 is correctly specified. Otherwise, the file cannot be upgraded using
-db5.2_upgrade, and must be upgraded manually using the
-db5.2_dump and db5.0_load utilities.
+db5.3_upgrade, and must be upgraded manually using the
+db5.3_dump and db5.0_load utilities.
 .IP \fB\-V\fR
 Write the library version number to the standard output, and exit.
 .IP \fB\-v\fR
@@ -59,16 +59,16 @@ system crashes during the upgrade procedure, or if the upgrade procedure
 runs out of disk space, the databases may be left in an inconsistent and
 unrecoverable state.
 .PP
-The db5.2_upgrade utility may be used with a Berkeley DB environment (as described for the
+The db5.3_upgrade utility may be used with a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_upgrade should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_upgrade
+Berkeley DB environment, db5.3_upgrade should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_upgrade
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_upgrade utility exits 0 on success, and >0 if an error occurs.
+The db5.3_upgrade utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
diff --git a/debian/manpages/db5.2_verify.1 b/debian/manpages/db5.3_verify.1
similarity index 78%
rename from debian/manpages/db5.2_verify.1
rename to debian/manpages/db5.3_verify.1
index f3d2cfb..304513b 100644
--- a/debian/manpages/db5.2_verify.1
+++ b/debian/manpages/db5.3_verify.1
@@ -1,13 +1,13 @@
 .\" Manual Page for Berkely DB utils, created from upstream
 .\" documentation by Thijs Kinkhorst <thijs@kinkhorst.com>.
-.TH DB5.2_VERIFY 1 "28 January 2005"
+.TH DB5.3_VERIFY 1 "28 January 2005"
 .SH NAME
-db5.2_verify \-  Verifies the structure databases
+db5.3_verify \-  Verifies the structure databases
 .SH SYNOPSIS
-.B db5.2_verify
+.B db5.3_verify
 [-NoqV] [-h home] [-P password] file ...
 .SH DESCRIPTION
-The db5.2_verify utility verifies the structure of one or more files and the
+The db5.3_verify utility verifies the structure of one or more files and the
 databases they contain.
 .SH OPTIONS
 .IP \fB\-h\fR
@@ -18,10 +18,10 @@ Skip the database checks for btree and duplicate sort order and for
 hashing.
 .sp
 If the file being verified contains databases with non-default
-comparison or hashing configurations, calling the db5.2_verify
+comparison or hashing configurations, calling the db5.3_verify
 utility without the \fB-o\fR flag will usually return failure.  The
-\fB-o\fR flag causes db5.2_verify to ignore database sort or
-hash ordering and allows db5.2_verify to be used on these files.
+\fB-o\fR flag causes db5.3_verify to ignore database sort or
+hash ordering and allows db5.3_verify to 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.
@@ -42,21 +42,21 @@ failure.
 .IP \fB\-V\fR
 Write the library version number to the standard output, and exit.
 .PP
-\fBThe db5.2_verify utility does not perform any locking, even in
+\fBThe db5.3_verify utility 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.\fR
 .PP
-The db5.2_verify utility may be used with a Berkeley DB environment (as described for the
+The db5.3_verify utility may be used with a Berkeley DB environment (as described for the
 \fB-h\fR option, the environment variable \fBDB_HOME\fR, 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, db5.2_verify should always be given the chance to
-detach from the environment and exit gracefully.  To cause db5.2_verify
+Berkeley DB environment, db5.3_verify should always be given the chance to
+detach from the environment and exit gracefully.  To cause db5.3_verify
 to release all environment resources and exit cleanly, send it an
 interrupt signal (SIGINT).
 .PP
-The db5.2_verify utility exits 0 on success, and >0 if an error occurs.
+The db5.3_verify utility exits 0 on success, and >0 if an error occurs.
 .SH ENVIRONMENT
 .IP \fBDB_HOME\fR
 If the \fB-h\fR option is not specified and the environment variable
-- 
1.9.0

