Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

apache::session::lock::semaphore(3pm) [debian man page]

Apache::Session::Lock::Semaphore(3pm)			User Contributed Perl Documentation		     Apache::Session::Lock::Semaphore(3pm)

NAME
Apache::Session::Lock::Semaphore - Provides mutual exclusion through semaphores SYNOPSIS
use Apache::Session::Lock::Semaphore; my $locker = new Apache::Session::Lock::Semaphore; die "no semaphores" unless $locker; $locker->acquire_read_lock($ref); $locker->acquire_write_lock($ref); $locker->release_read_lock($ref); $locker->release_write_lock($ref); $locker->release_all_locks($ref); DESCRIPTION
Apache::Session::Lock::semaphore fulfills the locking interface of Apache::Session. Mutual exclusion is achieved through system semaphores and the IPC::Semaphore module. CONFIGURATION
The module must know how many semaphores to use, and what semaphore key to use. The number of semaphores has an impact on performance. More semaphores means less lock contention. You should use the maximum number of semaphores that your platform will allow. On stock NetBSD, OpenBSD, and Solaris systems, this is probably 16. On Linux 2.2, this is 32. This module tries to guess the number based on your operating system, but it is safer to configure it yourself. To set the number of semaphores, you need to pass an argument in the usual Apache::Session style. The name of the argument is NSems, and the value is an integer power of 2. For example: tie %s, 'Apache::Session::Blah', $id, {NSems => 16}; You may also need to configure the semaphore key that this package uses. By default, it uses key 31818. You can change this using the argument SemaphoreKey: tie %s, 'Apache::Session::Blah', $id, {NSems => 16, SemaphoreKey => 42}; PROBLEMS
There are a few problems that people frequently encounter when using this package. If you get an invalid argument message, that usually means that the system is unhappy with the number of semaphores that you requested. Try decreasing the number of semaphores. The semaphore blocks that this package creates are persistent until the system is rebooted, so if you request 8 semaphores one time and 16 semaphores the next, it won't work. Use the system commands ipcs and ipcrm to inspect and remove unwanted semphore blocks. Cygwin IPC on Cygwin requires running cygserver. Without it, program will exit with "Bad System call" message. It cannot be intercepted with eval. Read /usr/share/doc/Cygwin/cygserver.README for more information. Darwin/MacOS X Darwin and MacOS X may not have semaphores, see <http://sysnet.ucsd.edu/~bellardo/darwin/sysvsem.html> *BSD Error "No space left on device" means that maximum number of semaphores is reached. See <http://www.postgresql.org/docs/7.3/static/kernel-resources.html> for more information. AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>. SEE ALSO
Apache::Session perl v5.10.1 2010-10-18 Apache::Session::Lock::Semaphore(3pm)

Check Out this Related Man Page

Apache::Session::Lock::File(3pm)			User Contributed Perl Documentation			  Apache::Session::Lock::File(3pm)

NAME
Apache::Session::Lock::File - Provides mutual exclusion using flock SYNOPSIS
use Apache::Session::Lock::File; my $locker = new Apache::Session::Lock::File; $locker->acquire_read_lock($ref); $locker->acquire_write_lock($ref); $locker->release_read_lock($ref); $locker->release_write_lock($ref); $locker->release_all_locks($ref); $locker->clean($dir, $age); DESCRIPTION
Apache::Session::Lock::File fulfills the locking interface of Apache::Session. Mutual exclusion is achieved through the use of temporary files and the "flock" function. CONFIGURATION
The module must know where to create its temporary files. You must pass an argument in the usual Apache::Session style. The name of the argument is LockDirectory and its value is the path where you want the lockfiles created. Example: tie %s, 'Apache::Session::Blah', $id, {LockDirectory => '/var/lock/sessions'} If you do not supply this argument, temporary files will be created in /tmp. NOTES
clean This module does not unlink temporary files, because it interferes with proper locking. This can cause problems on certain systems (Linux) whose file systems (ext2) do not perform well with lots of files in one directory. To prevent this you should use a script to clean out old files from your lock directory. The meaning of old is left as a policy decision for the implementor, but a method is provided for implementing that policy. You can use the "clean" method of this module to remove files unmodified in the last $age seconds. Example: my $l = new Apache::Session::Lock::File; $l->clean('/var/lock/sessions', 3600) #remove files older than 1 hour acquire_read_lock Will do nothing if write lock is in effect, only set readlock flag to true. release_read_lock Will do nothing if write lock is in effect, only set readlock flag to false. Win32 and Cygwin Windows cannot escalate lock, so all locks will be exclusive. release_read_lock not supported - it is not used by Apache::Session. When deleting files, they are not locked (Win32 only). AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>. SEE ALSO
Apache::Session perl v5.10.1 2010-10-18 Apache::Session::Lock::File(3pm)
Man Page