Im simply looking to check if an attempt to ssh to a host is successful, and nothing more. I have achieved this by the following :
close(STDERR) # ie I Dont want to see junk if ( &Net::SSH::ssh('user_that_fails@somehost', "exit") ) { print "A message - you just failed \n"; } else { print "A message - you just passed \n"; }
This seems to me to be the wrong way around, ie returns true when using a username that fails. More importantly, is there a better way of doing this ? ( sorry but I cant use Net::SSH::Perl ) NB - Not shown, but STDERR is saved off to a temp handle, and restored afterwards. Thanks.

Considered by jdporter: reap: dupe of Connection test : Net::SSH::Perl : $ssh->login - detecting failure
Unconsidered by Arunbear: keep (and edit) votes prevented reaping; Keep: 3, Edit: 1, Reap: 17


In reply to (DUPE) Is there a better way ? : Net::SSH - Detecting success or fail for a connection by jxh

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.