Hi, I'd like to use a OpenSSH connection in a MCE worker thread.

Doing so - the worker thread just exists after the "new".

First debugging:
not giving user/pwd it stops showing the password prompt.
giving user and pwd to the new - it crashes.

Is there any hassle with signals?
Any way out of that or how to do more debugging?

thanks for help, monks! :-> 


$self->sendto('stdout', "child($wid): doing ssh\n");     

$ssh = Net::OpenSSH->new(
    $device, 
    user => $sshuser, 
    passwd => $sshpwd,
    master_opts => [-o => "StrictHostKeyChecking=no"],
    master_stderr_discard => 1
);

$self->sendto('stdout', "child($wid): did ssh - not shown!!! \n");

[download]



and after some more digging: if I
use IO::Pty;
in the main prog already - everything is fine!
So there is not a signal but a coding issue in loading that lib during runtime..

In reply to using Net::OpenSSH in a MCE worker thread by Andy16

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.