tomfoolry,
Just a hunch, but is the output of scp being written to STDERR and not STDOUT?

Cheers - L~R

Update: Apparently not. I tried:
scp user@host:/path/to/file . >foo 2>bar
Without capturing the progress bar in either file. Incidently, you can turn the progress bar off with the -q option. I wasn't expecting this to produce a nice plain text output given the nature of how the progress bar works, but I would have at least expected something - odd.

Update 2: You might still be able to do what you want without the progress bar. If you disable the progress bar with -q but enable verosity with -v, then all the same information that is in -q can be read on STDERR. Incidently, scp exits with 0 on success and >0 on error.

In reply to Re: capture scp output by Limbic~Region
in thread capture scp output by tomfoolry

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.