go ahead... be a heretic | |
PerlMonks |
perlfunc:flockby gods (Initiate) |
on Aug 24, 1999 at 22:43 UTC ( [id://306]=perlfunc: print w/replies, xml ) | Need Help?? |
flockSee the current Perl documentation for flock. Here is our local, out-dated (pre-5.6) version: flock - lock an entire file with an advisory lock
flock FILEHANDLE,OPERATION
Calls
On many platforms (including most versions or clones of Unix), locks established by flock() are merely advisory. Such discretionary locks are more flexible, but offer fewer guarantees. This means that files locked with flock() may be modified by programs that do not also use flock(). Windows NT and OS/2 are among the platforms which enforce mandatory locking. See your local documentation for details. OPERATION is one of LOCK_SH, LOCK_EX, or LOCK_UN, possibly combined with LOCK_NB. These constants are traditionally valued 1, 2, 8 and 4, but you can use the symbolic names if import them from the Fcntl module, either individually, or as a group using the ':flock' tag. LOCK_SH requests a shared lock, LOCK_EX requests an exclusive lock, and LOCK_UN releases a previously requested lock. If LOCK_NB is added to LOCK_SH or LOCK_EX then flock() will return immediately rather than blocking waiting for the lock (check the return status to see if you got it). To avoid the possibility of mis-coordination, Perl flushes FILEHANDLE before (un)locking it.
Note that the emulation built with
Note also that some versions of flock() cannot lock things over the network; you would need to use the more
system-specific fcntl() for that. If you like you can force Perl to ignore your system's
Here's a mailbox appender for BSD systems.
use Fcntl ':flock'; # import LOCK_* constants
sub lock { flock(MBOX,LOCK_EX); # and, in case someone appended # while we were waiting... seek(MBOX, 0, 2); }
sub unlock { flock(MBOX,LOCK_UN); }
open(MBOX, ">>/usr/spool/mail/$ENV{'USER'}") or die "Can't open mailbox: $!";
lock(); print MBOX $msg,"\n\n"; unlock();
See also the DB_File manpage for other
|
|