This is what used to be called `locknix`.
The ``flufl.lock`` library provides an NFS-safe file-based locking algorithm
influenced by the GNU/Linux `open(2)` manpage, under the description of the
`O_EXCL` option::
[...] O_EXCL is broken on NFS file systems, programs which rely on it
for performing locking tasks will contain a race condition. The
solution for performing atomic file locking using a lockfile is to
create a unique file on the same fs (e.g., incorporating hostname and
pid), use link(2) to make a link to the lockfile. If link() returns
0, the lock is successful. Otherwise, use stat(2) on the unique file
to check if its link count has increased to 2, in which case the lock
is also successful.
This replaces http://
View full history Series and milestones
trunk series is the current focus of development.
All code Code
- Version control system:
- Bazaar
- Programming languages:
- Python
All packages Packages in Distributions
-
flufl.lock source package in Xenial
Version 2.4.1-1 uploaded -
flufl.lock source package in Trusty
Version 2.2.1-2 uploaded -
flufl.lock source package in Sid
Version 8.1.0-2 uploaded -
flufl.lock source package in Precise
Version 2.2-2 uploaded -
flufl.lock source package in Oracular
Version 8.1.0-1 uploaded
All bugs Latest bugs reported
-
Bug #1263794: Installation fails without access to http://pypi.python.org/
Reported -
Bug #1026403: pip installation instructions missing "install"
Reported -
Bug #977999: ENOENT vs ESTALE on NFS
Reported -
Bug #882261: In/Out error when aquiring lock
Reported -
Bug #872096: take_possession() uses the wrong _claimfile format
Reported