head 1.2; access; symbols RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2003.08.24.12.18.26; author rse; state dead; branches; next 1.1; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next ; desc @@ 1.2 log @Resolve: RPM 4.0.3 -> RPM 4.0.4 @ text @ Berkeley DB: DB_ENV->set_mutexlocks

DB_ENV->set_mutexlocks

#include <db.h> int DB_ENV->set_mutexlocks(DB_ENV *dbenv, int do_lock); Description Toggle mutex locks. Setting do_lock to a zero value causes Berkeley DB to grant all requested mutual exclusion mutexes and database locks without regard for their availability. This functionality should never be used for any other purpose than debugging. The DB_ENV->set_mutexlocks interface may be used to configure Berkeley DB at any time during the life of the application. The DB_ENV->set_mutexlocks function returns a non-zero error value on failure and 0 on success. See Also db_env_create, DB_ENV->close, DB_ENV->err, DB_ENV->errx DB_ENV->open, DB_ENV->remove, DB_ENV->set_alloc, DB_ENV->set_cachesize, DB_ENV->set_data_dir, DB_ENV->set_errcall, DB_ENV->set_errfile, DB_ENV->set_errpfx, DB_ENV->set_feedback, DB_ENV->set_flags, DB_ENV->set_mutexlocks, db_env_set_pageyield, DB_ENV->set_paniccall, db_env_set_panicstate, DB_ENV->set_recovery_init, DB_ENV->set_rpc_server, db_env_set_region_init, DB_ENV->set_shm_key, db_env_set_tas_spins, DB_ENV->set_tmp_dir, DB_ENV->set_verbose, db_strerror and db_version.