in reply to Net::OpenSSH error message

Just going out on a limb... I haven't used the OpenSSH module. "signal 1" is SIGHUP I believe. The is the "hangup" signal created when a controlling terminal disconnects from a running program (or a modem connection was terminated). In the old days, the command 'nohup' was used:
> nohup keep_running_after_I_hangup
Was used to trap the the SIGHUP and keep the child (it had spawned) processing after the modem line hung up (or the xterm closed).

Maybe something in the openSSH package is detecting the far end connection closing the socket (after piping the results back) and and treating it as a 'hangup/disconnect'.

It is always better to have seen your target for yourself, rather than depend upon someone else's description.

Replies are listed 'Best First'.
Re^2: Net::OpenSSH error message
by salva (Canon) on Oct 09, 2009 at 13:26 UTC

    Net::OpenSSH uses the HUP signal to kill the master SSH process when it does not exit "voluntarily" (probably it should be using TERM).

    Anyway, I would like to see the debugging output to ensure that this is the cause of the problem.