I used to use IPC::Open3 for this type of thing. Now I use AnyEvent::Util::run_cmd: 

use AnyEvent;
use AnyEvent::Util;
use File::Spec;

my ($stdout, $stderr) = ('', ''); # I think these need to be empty str
+ings, not undefs
my $pid;

my $cv = AnyEvent::Util::run_cmd [ qw(xcopy /Y /S /E /I /F /R /K), $so
+urce, $dest ],
  '<'  => File::Spec->devnull(),
  '>'  => \$stdout,
  '2>' => \$stderr,
  '$$' => \$pid, # this line is optional, you may not need it.
  ;

my $rc = $cv->recv();

[download]
(You can even run more than one of these at a time if you want, with a little extra code.)

In reply to Re: get stdout stderr by Tanktalus
in thread get stdout stderr by krosty

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.