Both options are needed.

Those errors are generated because you are requesting a TTY on the remote side but then there is no TTY on the local side and so when ssh tries to forward the ioctls, it gets that error back from the OS.

Other than redirecting STDERR to /dev/null (which is what stderr_discard actually does) I don't see how that message can be suppresed.

Use strace to see where are these msgs originate and where they go.

Update: Updating the local OpenSSH may also help as new versions generate fewer of these useless warnings.

In reply to Re^13: Problem using Net::OpenSSH->capture to su to another user by salva
in thread Problem using Net::OpenSSH->capture to su to another user by tim.culhane

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.