It actually took a little digging to find out how to properly handle the output and the various return codes of qx when executing an ssh command.

Why would you actually want to do such a thing to begin with? You wouldn't. Don't do it. Stop! For the love of ...

If, however, you have a machine who's operating system hasn't had a vendor supported upgrade any time this century, you may not have a choice.

I feel your pain. It runs deep, share it with me. 

sub ops_do_ssh_qx {
   my ($cmd) = @_;

   $cmd->{ssh_cmd_qx} = 'ssh ' .  $cmd->{user} . '\@' . $cmd->{host} .
+ ' \'' . $cmd->{command} . '\'' . ' 2>/dev/null';

   $cmd->{output} = qx($cmd->{ssh_cmd_qx});
   if ( defined $cmd->{output} ) {
      $cmd->{cmd_ret_code} = $?;
      chomp $cmd->{output};
      if ( $cmd->{cmd_ret_code} ) {
         $cmd->{success} = FAILURE;
      }
   }
   else {
      ($cmd->{ssh_ret_code}, $cmd->{ssh_ret_msg}) = (0 + $!, '' . $!);
      $cmd->{success} = FAILURE;
   }

   return $cmd;
}

[download]

The hash you pass in looks like this: 

my $cmd = { name => 'foo',
            user => 'foo_user',
            host => 'foo.bar.com',
            command => 'do_something_useful_here',
            success => SUCCESS
};

[download]

And you invoke it thusly: 

my $cmd_status = ops_do_ssh_qx($cmd);
if ( $cmd_status->{success} ) {
   do_something_with $cmd_status->{output};
}
else
{
   do_something_with $cmd_status->{cmd_ret_code}, $cmd_status->{ssh_re
+t_code}, $cmd_status->{ssh_ret_msg};
}

[download]

Unfortunately the values you end up with in 

   $cmd_status->{cmd_ret_code}
   $cmd_status->{ssh_ret_code}
   $cmd_status->{ssh_ret_msg}

[download]
are, for both the OS and SSH, implementation dependent, which is just one of the reasons you shouldn't be doing this if you have a choice.

If anybody finds this useful, you have my condolences.

Thanks,
cbeckley

Update: haukex has a great write up regarding alternatives to qx/backticks here Calling External Commands More Safely. My Perl was too old for the ones I tried, but afoken has indicated that piped opens are available even in 5.004.

In reply to Ssh and qx by cbeckley

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.