I haven't tried to use Net::OpenSSH(::Parallel), but the docs for Net::OpenSSH say that the $ssh->system() method accepts hash-style parameters for "default_stdout_file" and "default_stderr_file" (storing these outputs to named files), or "defailt_stdout_fh" and "default_stderr_fh" (passing file handles to receive these outputs).

So one approach might be, for each process in your queue, save stdout and stderr to distinct files (using different names for each process), and then read those files back when the ssh->system calls are all done.

I expect you could also open file handles that write to in-memory scalar variables (see description of open(FH,'>',\$variable) in the man page for open), pass those file handles to ssh->system() as default stdout/stderr, and then just do regex matches on those variables when the processes are done.

I think you'll want to use two separate outputs for each process (separating stderr and stdout), because each output of each process might operate asynchronously, and if more than one stream goes to a single file handle, the data might get interleaved in ways you wouldn't expect or want (e.g. a stderr message in the middle of a stdout line).

In reply to Re: How to capture process and redirect STDOUT in a hash by graff
in thread How to capture process and redirect STDOUT in a hash by thanos1983

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.