The quickest way to accomplish this is to avoid having to do it in the first place... Can your servers be configured to both send data to a single centralized log? I know *nix's syslog is network-aware and suspect something similar should exist for Apache and IIS, simply because companies with huge webserver farms aren't going to want to deal with each server's log individually.

If you're not able to centralize it, then duelafn's suggestion is probably going to be the quickest way to combine them. It also allows you to use tell on each filehandle before or after reading from it to monitor how far you've gotten in processing that file. Combined with checking the size of each file before starting, that should give you enough information to generate a relatively meaningful progress indicator.

In reply to Re: progress bar for a system command by dsheroh
in thread progress bar for a system command by xorl

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.