I think the file position keeps flipping back, because I see the message to STDERR report early blocks repeatedly.

Are you sure they're being reported repeatedly, or just somewhat out of order (which would be the expected behaviour due to runtime differences of the forked processes)?.

I just tried it (with a simple test file containing dummy SQL_REPORT_ID sections) on HP-UX 11.00, 11.11 and 11.23 with Perl 5.8.4 and 5.8.8, and I'm unable to reproduce the problem you describe. I.e., the proper $Sql content, $ReportId etc. are reported once each, as expected.

Are you doing anything else in the forked processes than what you've shown in the snippet above, or should that in fact already exhibit the problem?

In reply to Re: HPUX corruption of file handle after fork by almut
in thread HPUX corruption of file handle after fork by Abe

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.