Well, nothing stops you from pushing the retrieved data in an array instead of passing it to print. For instance:
$chan->shell(); print $chan "$cmd1\n"; @out1 = <$chan>; print $chan "$cmd2\n"; @out2 = <$chan>; ...

Unfortunately, Net::SSH2 is full of quirks and using it in the way you are doing is unreliable. You can see it if you run some slow commands, for instance, try $cmd1 = sleep 2.

If you are on a Linux/Unix system, your better option would be to switch to Net::OpenSSH.

Otherwise, you can use Net::SSH::Any which is able to run over Net::SSH2 and provides a friendlier interface while taking care of the ugly details for you... well, mostly, because there are several bugs on the current stable version of libssh2 that can not be worked around.


In reply to Re: Net::SSH2 to capture multiple commands on remote system by salva
in thread Net::SSH2 to capture multiple commands on remote system by bellis

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.