Look you loser,
Yipes! Major, major bad wei wu for that!

Let me explain carefully what I did. First I searched with quotes around the error string. I maintain that when one wants to find information about a specific error message that one must include the quotes so as to immediately filter out the extraneous hits that would otherwise match things like ssh. (Cluebat: In this context all those links out there that mention ssh in some random context are noise.) This search yielded two (2) hits (as mentioned above), both of which were for the OPs original node (one directly to the node, the other via SoPW).

Next I did it your way (sans quotes), which turned up 15k+ hits. The top hit there is to an html-ized rendering of the Net::OpenSSH sources. Of course this error message is there, but we already knew that, as the OP was kind enough to tell us that this error message was provided by the module in question. The next two hits are for the root node of this thread; the next is the one where you start calling me names, and the rest go off into that nether world of random links about ssh. As the question posed by the OP is about an error message from Net::OpenSSH, hoping to find something useful in those links seems like a waste of time.

The answer is in the first page of numerous links.

Well, then, if you're willing to be truly helpful and demonstrate some of your superior intelligence, please point to the specific google result that has you throwing fits like

You shouldn't be a programmer, you always check for string quoting errors in failed searches.... the class is called "Try_Harder_101"
I'm willing to learn the error(s) of my ways. Are you willing to teach? Or are you going to continue with the bovine birthing rituals?

In reply to Re^6: Net::OpenSSH killing script by Anonymous Monk
in thread Net::OpenSSH killing script by jaiieq

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.