IPC::ConcurrencyLimit::Lock::Flock - flock() based locking
This locking strategy implements
flock() based concurrency control. Requires that your system has a sane
flock() implementation as well as a non-blocking
Inherits from IPC::LimitConcurrency::Lock.
Take care not to attempt to use this on an NFS share or any other file system that does not implement atomic
Given a hash ref with options, attempts to obtain a lock in the pool. On success, returns the lock object, otherwise undef.
The directory that will hold the lock files. Created if it does not exist. It is suggested not to use a directory that may hold other data unless you also use the file_prefix option and ensure that your locks are unique.
An optional prefix which will be prepended to lock file names. If specified then files will be created that look like this:
By default lock files have a ".lock" suffix/extension. Set this option to specify a different extension.
The maximum no. of locks (and thus usually processes) to allow at one time.
In particular circumstance, you might want to set this to
shared. This subverts the way the normal concurrency limit works, but allows entirely different use cases.
Returns the full path and name of the lock file.
Returns the directory in which the lock files resides.
This module was originally developed for booking.com. With approval from booking.com, this module was generalized and put on CPAN, for which the authors would like to express their gratitude.
(C) 2011, 2012 Steffen Mueller. All rights reserved. This code is available under the same license as Perl version 5.8.1 or higher. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.