1<!--$Id: mutexlock.so,v 1.4 2003/10/18 19:16:16 bostic Exp $--> 2<!--Copyright (c) 1997,2008 Oracle. All rights reserved.--> 3<!--See the file LICENSE for redistribution information.--> 4<html> 5<head> 6<title>Berkeley DB Reference Guide: Release 3.2: DB_ENV->set_mutexlocks</title> 7<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> 8<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> 9</head> 10<body bgcolor=white> 11<table width="100%"><tr valign=top> 12<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></b></td> 13<td align=right><a href="../upgrade.3.2/tx_recover.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.3.2/handle.html"><img src="../../images/next.gif" alt="Next"></a> 14</td></tr></table> 15<p align=center><b>Release 3.2: DB_ENV->set_mutexlocks</b></p> 16<p>Previous Berkeley DB releases included the db_env_set_mutexlocks function, 17intended for debugging, that allows applications to always obtain 18requested mutual exclusion mutexes without regard for their 19availability. This function has been replaced with 20dbenv_set_mutexlocks, which provides the same functionality on a 21per-database environment basis. Applications using the old function 22should be updated to use the new one.</p> 23<table width="100%"><tr><td><br></td><td align=right><a href="../upgrade.3.2/tx_recover.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.3.2/handle.html"><img src="../../images/next.gif" alt="Next"></a> 24</td></tr></table> 25<p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> 26</body> 27</html> 28
