db_dump185(8) [osf1 man page]
db_dump(8) System Manager's Manual db_dump(8) NAME
db_dump, db_dump185 - Reads and writes the security databases (Enhanced Security) SYNOPSIS
/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 FLAGS
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. DESCRIPTION
A customized version of the Berkeley Database (Berkeley DB) is embedded in the operating system to provide high-performance database sup- port for critical security files. The DB includes full transactional support and database recovery, using write-ahead logging and check- pointing to record changes. The db_dump utility reads the security database file db_file and writes it to the standard output using a portable flat-text format under- stood 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 similar 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 UNIX. Dumping and reloading hash databases that use user-defined hash functions 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 prefix and comparison functions. In this case, it is quite likely that the database will be damaged beyond repair permitting neither record storage 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. RETURN VALUES
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. ENVIRONMENT VARIABLES
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. FILES
/var/tcb/files/auth.db /var/tcb/files/dblogs/* RELATED INFORMATION
Commands: edauth(8), db_load(8) delim off db_dump(8)
Check Out this Related Man Page
db_load(8) System Manager's Manual db_load(8) NAME
db_load - Loads standard input to a database files (Enhanced Security) SYNOPSIS
/usr/tcb/bin/db_load [-nT] [-c name=value] [-f file] [-h home] [-t btree|hash|recno] db_file FLAGS
Specify configuration options for the DB_INFO structure provided to db_open ignoring any value they may have been based on the input. The command-line format is name=value. The following keywords are supported: The minimum number of keys per page. The byte order for integers in the stored database metadata. The size of pages used for nodes in the tree, in bytes. The value of the DB_DUP flag. The density within the hash table. The size of the hash table. Specify fixed-length records of the specified length. Specify the fixed-length record pad character. The value of the DB_RECNUM flag. The value of the DB_RENUMBER flag. The parenthetical listing specifies how the value part of the name=value pair is interpreted. Items listed as (boolean) expect value to be 1 (set) or 0 (unset). Items listed as (number) convert value to a number. Items listed as (string) use the characters of value directly. Read from the specified input file, instead of from the standard input. Specify a home directory for the database. The correct directory for enhanced security is /var/tcb/files. Do not overwrite existing keys in the database when loading into an already existing database. If a key/data pair cannot be loaded into the database for this reason, a warning message is displayed on the standard error output and the key/data pair are skipped. The -T option allows non-Berkeley DB applications to easily load text files into databases. If the database to be created is of type btree or hash, the input must be paired lines of text, where the first line of the pair is the key item, and the second line of the pair is its corresponding data item. If the database to be created is of type recno, the input must be lines of text, where each line is a new data item for the database. A simple escape mechanism, where newline and backslash () characters are special, is applied to the text input. Newline characters are interpreted as record separators. Backslash characters in the text will be interpreted in one of two ways: If the backslash character pre- cedes another backslash character, the pair will be interpreted as a literal backslash. If the backslash character precedes any other character, the two characters following the backslash will be interpreted as hexadecimal specification of a single character, that is, a is a newline character in the ASCII character set. For this reason, any backslash or newline characters that naturally occur in the text input must be escaped to avoid misinterpretation by db_load. If the -T option is specified, the underlying access method type must be specified using the -t option. Specifies the underlying access method. If no -t option is specified, the database will be loaded into a database of the same type as was dumped, that is, a hash database is created if a hash database was dumped. The btree and hash databases may be converted from one to the other. The recno databases may not be converted to any other database type or from any other database type. DESCRIPTION
A customized version of the Berkeley Database (Berkeley DB) is embedded in the operating system to provide high-performance database sup- port for critical security files. The DB includes full transactional support and database recovery, using write-ahead logging and check- pointing to record changes. The db_load utility reads from the standard input and loads it into the db_file database . The database db_file is created if it does not already exist. The input to db_load must be in the output format specified by the db_dump utility or as specified for the -T option. The db_load utility utility attaches to one or more of the Berkeley DB shared memory regions. In order to avoid region corruption, it should always be given the chance to detach and exit gracefully. To cause db_load to clean up after itself and exit, send it an interrupt signal (SIGINT). The db_load utility can be used to load text files into the security databases. It is used by Tru64 UNIX utilities and is not recommended for use by system administration. The edauth utility provides a supported means of loading records correctly into the security databases. RETURN VALUES
The db_load utility exits 0 on success, and >0 if one or more key/data pairs were not loaded into the database because the key already existed, and with >1 if an error occurs. ENVIRONMENT VARIABLES
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. FILES
/var/tcb/files/auth.db /var/tcb/files/dblogs/* RELATED INFORMATION
Files: authcap(4) Commands: edauth(8), db_dump(8) delim off db_load(8)