I think that I would separate the concerns by prefiltering the files and feeding each thread's lines to different processes via pipes:

#! perl use strict; #### Warning! Untested code -- just an example. for my $log ( <*.log> ) { open my $fhLog, '<', $log or die $!; my %kids; while( <$fhLog> ) { my( $tid ) = m[\(([0-9A-F]+)\)]; if( not exists $kids{ $tid } ) { my $pid = open my $fh, '|-', 'perl non-interleaved.pl' or +die $!; $kids{ $tid } = [ $pid, $fh ]; } print { $kids{ $tid }[ 1 ] } $_; } for my $kid ( keys %kids ) { close $kid->[ 1 ]; ## close the pipe waitpid $kid->[ 0 ], 0; ##wait for the kid to finish rename $log, "archive/$log"; ## move the file } }

This way, you don't have to accumulate lots of lines in memory in order to get complete transactions. The same simplified non-interleaved.pl deals with each threads data, and deals with just one transaction at a time.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP PCW It is as I've been saying!(Audio until 20090817)

In reply to Re: Interlaced log parser by BrowserUk
in thread Interlaced log parser by tzen

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.