If you fork() for every file, you can use a hash to store the information. This doesn't include all of the SFTP stuff, but hopefully its enough to give you an idea you can merge in with the callback sub feature of Net::SFTP::Foreign.

use warnings; use strict; use Data::Dumper; use Parallel::ForkManager; my @files = qw(one.txt two.txt); my %info; my $pm = Parallel::ForkManager->new; FILE: for my $file (@files){ $pm->start and next FILE; $info{$file}{size} = -s $file; $pm->finish; } $pm->wait_all_children; print Dumper \%info; __END__ $VAR1 = { 'two.txt' => { 'size' => 21 }, 'one.txt' => { 'size' => 30 } };

Then you can process the collected data after all the workers have finished.


In reply to Re: Net::SFTP::Foreign Transferred Bytes by stevieb
in thread Net::SFTP::Foreign Transferred Bytes by yulivee07

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.