head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.56.40; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.38; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.38; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.13; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.49.04; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.07.23.20.09.19; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.05.01; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: db_verify

db_verify

db_verify [-NqV] [-h home] file ... Description The db_verify utility verifies the structure of one or more files and the databases they contain. The options are as follows: -h Specify a home directory for the database environment; by default, the current working directory is used. -N Do not acquire shared region locks 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. -q Suppress the printing of any error descriptions, simply exit success or failure. -V Write the library version number to the standard output, and exit. The db_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. If the file being verified contains databases using non-default comparison or hashing functions, the db_verify utility may not be used for verification, as it will likely always return failure. Such files must be verified explicitly, using the DB->verify function, after setting the correct comparison or hashing functions. The db_verify utility may be used with 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, db_verify should always be given the chance to detach from the environment and exit gracefully. To cause db_verify to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). The db_verify utility exits 0 on success, and >0 if an error occurs. Environment Variables DB_HOME 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, as described in DB_ENV->open. See Also berkeley_db_svc, db_archive, db_checkpoint, db_deadlock, db_dump, db_load, db_recover, db_stat, db_upgrade, and db_verify.

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d21 1 a21 1

db_verify [-NoqV] [-h home] [-P password] file ...

d30 4 a33 19

-o

Skip the database checks for btree and duplicate sort order and for hashing.

If the file being verified contains databases using non-default comparison or hashing functions, calling the db_verify utility without the -o flag will usually return failure. The -o flag causes db_verify to ignore database sort or hash ordering and allows db_verify to be used on these files. To fully verify these files, verify them explicitly using the DB->verify method, after setting the correct comparison or hashing functions.

-N

Do 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.

-P

Specify 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. d39 8 a46 3 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. d62 12 @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d22 1 a22 1

db_verify [-NqV] [-h home] file ...

d31 19 a49 4

-N

Do not acquire shared region locks 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. d55 3 a57 8 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.

If the file being verified contains databases using non-default comparison or hashing functions, the db_verify utility may not be used for verification, as it will likely always return failure. Such files must be verified explicitly, using the DB->verify function, after setting the correct comparison or hashing functions. a72 12