You can capture or redirect the STDERR channel at will, just like any filehandle. This should work for operations that are shelled out as well. Details are in open, but a simple bit of code looks like: 

#!/usr/bin/perl
use warnings;
use strict;

open my $olderror, ">&STDERR" or die "Can't dup STDERR: $!";
open STDERR, ">&STDOUT" or die "Can't dup STDOUT: $!";

warn "This is sent on STDOUT\n";

open STDERR, ">&", $olderror or die "Can't dup \$olderror: $!";

warn "This is sent on STDERR\n";

[download]

Note STDERR, like all bareword filehandles, is global in scope and so you might be messing in someone else's backyard. Note as well you'll probably want to restore the channel, as I have, when you are done with it.

In reply to Re: How to capture Net::SFTP::Foreign output by kennethk
in thread How to capture Net::SFTP::Foreign output by tdwilson58

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.