Thus far, in our 2300+ server environment I have NOT come across a set of SSH options that can account for when a process becomes hung on the remote server, such as rpm, df, bdf, getconf, ioscan, flaky sshd, etc... That is why one may need to kill the process and prevent script lock
There isn't an easy and general way to handle remote commands hung. Killing the local ssh process is not enough as it may leave the remote processes running.
IMO, the best approach is to try to identify the pid of the remote process and kill it running kill also via ssh on the remote host (setting ServerAliveInterval and ServerAliveCountMax should be enough to detect hung sessions due to connection errors).
Passwords and Pass Phrases could easily be addressed as the IPC::Open3 call provides STDIN, STDOUT, and STDERR
It is not that easy! ssh does not use STDIN/STDOUT for authentication dialogs but /dev/tty. Getting that right is pretty tricky.
Try to do it while limiting yourself to the modules provided with ActiveState Perl or try to make it work under Windows!
In reply to Re^5: making NET:SSH quiet
by salva
in thread making NET:SSH quiet
by Stoomy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |