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) Safe-mode: OFF (not secure) /usr/share/doc/db4-devel-4.3.27/ref/log/ drwxr-xr-x |
Viewing file: Select action/file-type:
Berkeley DB and loggingThe Logging subsystem is the logging facility used by Berkeley DB. It is largely Berkeley DB-specific, although it is potentially useful outside of the Berkeley DB package for applications wanting write-ahead logging support. Applications wanting to use the log for purposes other than logging file modifications based on a set of open file descriptors will almost certainly need to make source code modifications to the Berkeley DB code base. A log can be shared by any number of threads of control. The DB_ENV->open method is used to open a log. When the log is no longer in use, it should be closed using the DB_ENV->close method. Individual log entries are identified by log sequence numbers. Log sequence numbers are stored in an opaque object, a DB_LSN. The DB_ENV->log_cursor method is used to allocate a log cursor. Log cursors have two methods: DB_LOGC->get method to retrieve log records from the log, and DB_LOGC->close method to destroy the cursor. There are additional methods for integrating the log subsystem with a transaction processing system:
Copyright (c) 1996-2004 Sleepycat Software, Inc. - All rights reserved. |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #16 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0041 ]-- |