File locking with fcntl(2)
http://search.cpan.org/dist/File-FcntlLock/
File locking in Perl is usually done using the the flock() manpage
function. Unfortunately, this only allows locks on whole files and is often
implemented in terms of flock(2), which has some shortcomings.
Using this module file locking via fcntl(2) can be done.
- Developed at devel:languages:perl
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:16.0:FactoryCandidates/perl-File-FcntlLock && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
File-FcntlLock-0.20.tar.gz | 0000016801 16.4 KB | |
perl-File-FcntlLock.changes | 0000001816 1.77 KB | |
perl-File-FcntlLock.spec | 0000003479 3.4 KB |
Revision 4 (latest revision is 6)
Stephan Kulow (coolo)
accepted
request 242342
from
Stephan Kulow (coolo)
(revision 4)
- updated to 0.20 - Problem on GNU Hurd hopefully fixed and some cosmetic changes. 0.19 Tue May 27 2014 - Builds failed on 32-bit systems due to missing CFLAGS derived from the Perl installation. 0.18 Mon May 26 2014 - CPAN didn't find the version number in FcntlLock.pm which was derived from that of Core.pm:-( 0.17 Mon May 26 2014 - CPAN testing showed that there are 32-bit systems where the off_t member of the flock struct is a 64-bit integer but Perl doesn't support the 'q' format for pack() and unpack(). On these systems there seem to be no good way of assembling a flock structure useing "pure Perl" and thus the File::FcntlLock::Pure and File::FcntlLock::Inline modules won't get installed. 0.16 Sun May 25 2014 - Missing file in 0.15, Pure.pm, in MANIFEST added. 0.15 Thu May 20 2014 - Module rewritten as three modules, one working exactly as before, and two new ones that instead of being XS-based use Perl code. For the first one the Perl code for packing/unpacking the C flock struct is generated when 'perl Makefile.PL' is run. For the other a C program is created, compiled and run each time the module gets loaded. This is in response to some concerns
Comments 0