Update: tye is absolutely right in his answer. My auto-answer below was written before seeing it. Still, tye++.


The power of this monastery is incredible. After posting my question and getting a nice night of sleep, inspiration came to me. It turns out that the real problem, was the time() at which I wrote that code.

Anyhow, the piece of code below (based on the one posted above) illustrates how to correctly use flock() to acquire exclusive access on a file. As a hint, always try to lock the same file from all your processes :)

#!/usr/bin/perl use strict; use warnings; use IO::File; use Fcntl qw(:flock); our $lock_file = 'test_lck'; # Get rid of our garbage END { unlink $lock_file; }; our %fh; my $id = 'A'; my $pid; my $buf = 'nothing'; $|++; # Spawn one helpful kid... while (($pid = fork()) == -1) { sleep 2; } unless ($pid) { # This is our child ++ $id; END {}; my $fh = new IO::File "$lock_file", O_RDWR | O_CREAT or die "Failed to open $lock_file: $!\n"; print "$id: about to lock...\n"; unless (flock($fh, LOCK_EX | LOCK_NB)) { die "$id: Failed to acquire lock: $!\n"; } print "$id: done\n"; print "$id: wrote\n"; $fh->syswrite("$id\n", 3); print "$id: seeked\n"; $fh->seek(0, 0); sleep 3; print "$id: read\n"; $fh->sysread($buf, 3); chomp $buf; print "$id: got <$buf>\n"; flock($fh, LOCK_UN); $fh->close; exit 0; } my $fh = new IO::File "$lock_file", O_RDWR | O_CREAT or die "Failed to open $lock_file: $!\n"; print "$id: about to lock...\n"; if (flock($fh, LOCK_EX | LOCK_NB)) { print "$id: done\n"; print "$id: wrote\n"; $fh->syswrite("$id\n", 3); print "$id: seeked\n"; $fh->seek(0, 0); print "$id: read\n"; $fh->sysread($buf, 3); sleep 2; chomp $buf; print "$id: got <$buf>\n"; flock($fh, LOCK_UN); } else { print "$id: Failed to acquire lock: $!\n"; } $fh->close; wait(); # Collect our child status exit 0;

This now produces the expected output in my system:

bash-2.05a$ ./flock-test.pl 
B: about to lock...
B: done
B: wrote
B: seeked
A: about to lock...
A: Failed to acquire lock: Resource temporarily unavailable
B: read
B: got <B>

Thanks a lot to the monks that read my post.

-lem, but some call me fokat


In reply to Re: Testing flock by fokat
in thread Testing flock by fokat

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.