Change 13824 by jhi@alpha on 2001/12/21 01:14:12
Subject: perlfunc.pod patch re flock via fcntl
From: "Tye McQueen" <[EMAIL PROTECTED]>
Date: Thu, 20 Dec 2001 14:52:19 -0600 (CST)
Message-Id: <[EMAIL PROTECTED]>
Affected files ...
.... //depot/perl/pod/perlfunc.pod#285 edit
Differences ...
==== //depot/perl/pod/perlfunc.pod#285 (text) ====
Index: perl/pod/perlfunc.pod
--- perl/pod/perlfunc.pod.~1~ Thu Dec 20 18:30:05 2001
+++ perl/pod/perlfunc.pod Thu Dec 20 18:30:05 2001
@@ -1658,6 +1658,10 @@
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<flock> cannot lock things over the
network; you would need to use the more system-specific C<fcntl> for
that. If you like you can force Perl to ignore your system's flock(2)
End of Patch.
