db_dump, db_dump185 - Reads and writes the security databases (Enhanced
/usr/tcb/bin/db_dump [-dN] [-f output] db_file
[/usr/tcb/bin/db_dump] [-p] [-f output] [-h home] db_file
[/usr/tcb/bin/db_dump185] [-p] [-f output] db_file
Dump the specified database in a format helpful for debugging the
Berkeley DB library routines. The output format of the -d option is not
standard and may change without notice between releases of the Berkeley
DB library. Write to the specified file instead of to the standard
output Specify a home directory for the database. The correct directory
for enhanced security is /var/tcb/files. Do not acquire shared region
locks while searching the database. This option is intended only for
debugging and should not be used under any other circumstances. If
characters in either the key or data items are printing characters (as
defined by isprint, use printing characters in file to represent them.
This option permits users to use standard text editors and tools to
modify the contents of databases.
A customized version of the Berkeley Database (Berkeley DB) is embedded
in the operating system to provide high-performance database support
for critical security files. The DB includes full transactional support
and database recovery, using write-ahead logging and checkpointing to
The db_dump utility reads the security database file db_file and writes
it to the standard output using a portable flat-text format understood
by the db_load utility.
The db_dump and db_dump185 utilities are included in Tru64 UNIX for use
by installation and update utilities, and are not recommended for use
by system administration. The edauth utility provides a supported means
of copying records from the security databases.
Earlier versions of Tru64 UNIX used Version 1.85 of the Berkeley DB for
enhanced security databases. So the db_dump185 utility, which is simi‐
lar to the db_dump utility except that it reads databases in the format
used by Berkeley DB Versions 1.85 and 1.86, is included with Tru64
Dumping and reloading hash databases that use user-defined hash func‐
tions will result in new databases that use the default hash function.
While using the default hash function may not be optimal for the new
database, it will continue to work correctly.
Dumping and reloading btree databases that use a user-defined prefix or
comparison functions results in new databases that use the default pre‐
fix and comparison functions. In this case, it is quite likely that the
database will be damaged beyond repair permitting neither record stor‐
age or retrieval.
The only available workaround for either case is to modify the sources
for the db_load utility to load the database using the correct hash,
prefix and comparison functions.
The db_dump utility exits 0 on success, and >0 if an error occurs.
The db_dump185 utility exits 0 on success, and >0 if an error occurs.
If the -h option is not specified and the environment variable DB_HOME
is set, it is used as the path of the database home. The home directory
for security is /var/tcb/files.
Commands: edauth(8), db_load(8)db_dump(8)