Software: Apache/2.0.54 (Fedora). PHP/5.0.4 

uname -a: Linux mina-info.me 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 

uid=48(apache) gid=48(apache) groups=48(apache)
context=system_u:system_r:httpd_sys_script_t 

Safe-mode: OFF (not secure)

/usr/share/doc/db4-devel-4.3.27/ref/upgrade.4.0/   drwxr-xr-x
Free 3.56 GB of 27.03 GB (13.18%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     lock.html (3.32 KB)      -rw-r--r--

Berkeley DB Reference Guide: Upgrading Berkeley DB Applications

Release 4.0: lock_XXX

The C API for the Berkeley DB Locking subsystem was reworked in the 4.0 release as follows:

Applications calling any of these functions should update their calls to use the enclosing DB_ENV handle's method (easily done as the first argument to the existing call is the correct handle to use).

In addition, the DB_ENV->lock_stat call has been changed in the 4.0 release to take a flags argument. To leave their historic behavior unchanged, applications should add a final argument of 0 to any calls made to DB_ENV->lock_stat.

The C++ and Java APIs for the DbLock::put (DbLock.put) method was reworked in the 4.0 release to make the lock put interface a method of the DB_ENV handle rather than the DbLock handle. Applications calling the DbLock::put or DbLock.put method should update their calls to use the enclosing DB_ENV handle's method (easily done as the first argument to the existing call is the correct handle to use).

Copyright (c) 1996-2004 Sleepycat Software, Inc. - All rights reserved.