This may not exactly be related to your problem, but I've recently had some experience on working with Net::SSH::Expect. I wanted to execute programs (which can be interactive) on multiple hosts via SSH and capture the output for each of them and used Net::SSH::Expect for this.
During the course noticed that there are some serious issues with how Net::SSH::Expect::read_all() determines termination of any command. It follows a logic of timeout duration of inactivity on the input stream - the command's STDOUT - to decide it's termination. Which can be highly misleading. I had to tweak some of Net::SSH::Expect's code to work around this.
In reply to Re: Connection Failing for unknown reason
by laminee
in thread Connection Failing for unknown reason
by sierpinski
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |