head	1.1;
access;
symbols
	pkgsrc-2026Q1:1.1.0.20
	pkgsrc-2026Q1-base:1.1
	pkgsrc-2025Q4:1.1.0.18
	pkgsrc-2025Q4-base:1.1
	pkgsrc-2025Q3:1.1.0.16
	pkgsrc-2025Q3-base:1.1
	pkgsrc-2025Q2:1.1.0.14
	pkgsrc-2025Q2-base:1.1
	pkgsrc-2025Q1:1.1.0.12
	pkgsrc-2025Q1-base:1.1
	pkgsrc-2024Q4:1.1.0.10
	pkgsrc-2024Q4-base:1.1
	pkgsrc-2024Q3:1.1.0.8
	pkgsrc-2024Q3-base:1.1
	pkgsrc-2024Q2:1.1.0.6
	pkgsrc-2024Q2-base:1.1
	pkgsrc-2024Q1:1.1.0.4
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.2
	pkgsrc-2023Q4-base:1.1;
locks; strict;
comment	@# @;


1.1
date	2023.11.16.08.54.16;	author adam;	state Exp;
branches;
next	;
commitid	pOhAl35azfqFsOME;


desc
@@


1.1
log
@p5-File-FcntlLock: added version 0.22

Using this module file locking via fcntl(2) can be done (obviously, this
restricts the use of the module to systems that have a fcntl(2) system call).
Before a file (or parts of a file) can be locked, an object simulating a flock
structure, containing information in a binary format to be passed to fcntl(2)
for locking requests, must be created and its properties set. Afterwards, by
calling the lock() method a lock can be set and removed or it can be determined
if and which process currently holds the lock.
@
text
@Using this module file locking via fcntl(2) can be done (obviously, this
restricts the use of the module to systems that have a fcntl(2) system call).
Before a file (or parts of a file) can be locked, an object simulating a flock
structure, containing information in a binary format to be passed to fcntl(2)
for locking requests, must be created and its properties set. Afterwards, by
calling the lock() method a lock can be set and removed or it can be determined
if and which process currently holds the lock.
@