I'm not sure how much less code it would be with threads since threads don't easily share data between them, and I need to pull all the data from all the subprocesses back together at the end. So I'd be exchanging one large chunk of code for another. In general, I'm more familiar with IPC::Open3 and IO::Select than ithreads, so I chose this way due to familiarity. Now, if that's the only option I have for eliminating this intermittent issue, I'm more than willing to try it, but it'll be hard to prove ;-)

As for upgrading perl, I thought I addressed that in the original node. I will be pursuing the upgrade of perl, regardless of this issue, anyway. But it'll take time to get through all the lawyers and managers.


In reply to Re^2: Modification of read-only value by Tanktalus
in thread Modification of read-only value by Tanktalus

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.