Trying to reproduce this under HPUX (which I was able to do), I see that the second flock() fails with $! of "Bad file number" [even though fileno(FH) reports 3]. Smells like a bug in Perl's emulation of flock() using fcntl() locking [since HPUX doesn't have native flock()]. I think I'll dig some more...

Update! Here is the reason. Quoting "man fcntl":

The file descriptor on which a read lock is being placed must have been opened with read access.

So, since you don't open FH for read access, you can't get an emulated LOCK_SH on it at all. I wonder if Perl documents this... (nope, it doesn't -- time to write a patch).

So, of course, the work-around is to open "+>lock" instead.

        - tye (but my friends call me "Tye")

In reply to (tye)Re: flock on differents OSes by tye
in thread flock on differents OSes by philou

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.