You may be suffering from buffering, and from misuse of flock. Update: This assertion is incorrect; Perl handles it correctly now.

LOCK_UN unlocks the file, removing the advisory lock before you closed the file. Remember that close flushes the output buffer if there's anything still in it. So it's entirely possible that your lock has been removed before the buffer gets flushed.

The solution is to not call flock($fh, LOCK_UN) or ..., but rather, to call close $fh or ..., at which time the lock will be cleared after flushing.

If this doesn't clear up your problem, then you have another bug in addition to the one demonstrated in the code you provided.


Dave

In reply to Re: Question about flock and printing to file by davido
in thread Question about flock and printing to file by deruytja

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.