From becacb537d97b70deefeaf2a3a313bb48d52e820 Mon Sep 17 00:00:00 2001 From: Tye McQueen Date: Thu, 20 Dec 2001 08:52:19 -0600 Subject: [PATCH] perlfunc.pod patch re flock via fcntl Message-Id: <200112202052.fBKKqKH16263@metronet.com> p4raw-id: //depot/perl@13824 --- pod/perlfunc.pod | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index e5f322c..1d65ca6 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -1658,6 +1658,10 @@ are the semantics that lockf(3) implements. Most if not all systems implement lockf(3) in terms of fcntl(2) locking, though, so the differing semantics shouldn't bite too many people. +Note that the fcntl(2) emulation of flock(3) requires that FILEHANDLE +be open with read intent to use LOCK_SH and requires that it be open +with write intent to use LOCK_EX. + Note also that some versions of C cannot lock things over the network; you would need to use the more system-specific C for that. If you like you can force Perl to ignore your system's flock(2) -- 2.7.4