Here's some sample code, using Perl's flock function, that I've used for many years on both Unix and Windows,
to ensure only one copy of a script is running at a time.
use Fcntl ':flock'; # import LOCK_* constants
warn "program starts\n";
my $somelockfile = 'choosealockfilename'; # adjust according to you
open(my $fhlock, '>', $somelockfile) or die "Error: open '$somelockfil
warn "before flock: filename='$somelockfile'\n";
# Note: process will block at this point until the lock is acquired.
flock($fhlock, LOCK_EX) or die "Error: flock '$somelockfile': $!";
# Lock is now held until $fhlock is closed.
# Note that even if this program crashes or is killed, $fhlock will
# be closed by the OS and the lock released.
warn "Got lock, sleeping for 10 secs...\n";
warn "woke up\n";
# Release the lock simply by closing the file handle.
close $fhlock or die "Error: close '$somelockfile': $!";
warn "lock released: sleeping for 5 secs...\n";
warn "program ends\n";
You can easily test its behaviour by running the little test program above in two different terminal sessions
(and either waiting for the sleep to end or manually killing one of the processes).
Apart from providing portable locking across Unix and Windows, flock has long been a favourite
of Perl poets, as beautifully shown by pjf in this immortal line:
join flock($other,@chickens) if split /from others/;
from his classic poem my @chickens
(by the way,
is one of the few monks I've met in real life; in addition to running chickens in his backyard, he has a keen interest in picking and eating unusual and delicious wild plants you won't find in any supermarket ... not for the faint-hearted, you need a keen eye and expert knowledge to avoid being poisoned).
Update: See also: File Locking Tricks and Traps by MJD (mentioned by davido below). And Ensuring only one copy of a perl script is running at a time from 2006. And Highlander - allow only one invocation at a time of an expensive CGI script by merlyn from 2000. From 2021: File lock demo by LanX and singleton lock not reliable by pidloop.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.