dbm::deep::storage(3pm) debian man page | unix.com

Man Page: dbm::deep::storage

Operating Environment: debian

Section: 3pm

DBM::Deep::Storage(3pm) 				User Contributed Perl Documentation				   DBM::Deep::Storage(3pm)

NAME
DBM::Deep::Storage - abstract base class for storage flush() This flushes the filehandle. This takes no parameters and returns nothing. is_writable() This takes no parameters. It returns a boolean saying if this filehandle is writable. Taken from <http://www.perlmonks.org/?node_id=691054/>.
LOCKING
This is where the actual locking of the storage medium is performed. Nested locking is supported. NOTE: It is unclear what will happen if a read lock is taken, then a write lock is taken as a nested lock, then the write lock is released. Currently, the only locking method supported is flock(1). This is a whole-file lock. In the future, more granular locking may be supported. The API for that is unclear right now. The following methods manage the locking status. In all cases, they take a DBM::Deep object and returns nothing. o lock_exclusive( $obj ) Take a lock usable for writing. o lock_shared( $obj ) Take a lock usable for reading. o unlock( $obj ) Releases the last lock taken. If this is the outermost lock, then the object is actually unlocked. perl v5.14.2 2012-06-24 DBM::Deep::Storage(3pm)
Related Man Pages
pthread_rwlock_unlock(3c) - sunos
dotlock(1) - debian
pthread_rwlock_unlock(3t) - hpux
dbm::deep::engine(3pm) - debian
inn::utils::shlock(3pm) - debian
Similar Topics in the Unix Linux Community
Adding the individual columns of a matrix.
awk or sed - Convert 2 lines to 1 line
Introduction
Weird 'find' results
New UNIX and Linux History Sections