Bug #56403 for IPC-Run: IPC::Run::run not timeout properly when run command via ssh

Thu Apr 08 15:50:12 2010 http://www.google.com/profiles/jbao605 - Ticket created

Subject:

IPC::Run::run not timeout properly when run command via ssh

If I run an external command on localhost using IPC::Run, I can timeout it properly my ($in, $out, $err, @cmd); @cmd = ("/bin/true”); run \@cmd, \$in, \$out, \$err, timeout(5), debug => 1; The above script would finish in less than 0.1 seconds. However, if the command contains ssh, i.e., I am running the command on another host via ssh, timeout doesn’t work: @cmd = ("ssh", "anotherhost", "/bin/true"); run \@cmd, \$in, \$out, \$err, timeout(5); This code would take 6.534 seconds to finish. Note that I am using a dummy hostname above. For the actual host, ssh works fine. Running the entire command including ssh in a shell finishes in less than one second. If I increase the timeout, the time it took to finish would increase accordingly. For example, if the timeout is set to 10 seconds, the actual time it took the script to finish would be 11.529 seconds. I'd appreciate if anybody has any input on this, or maybe I am missing something in the doc completely? Thanks J Bao

Thu Apr 08 16:55:34 2010 TODDR [...] cpan.org - Correspondence added

I'm not saying this isn't a bug, but if the problem is only with ssh, I'd encourage you to look at Net::OpenSSH, which specifically focuses on interfacing with ssh. I've found it very useful in the past. Note that you must be interfacing with Open SSH in order for this to work for you.

Thu Apr 08 16:55:38 2010 The RT System itself - Status changed from 'new' to 'open'

Thu Apr 08 16:56:38 2010 TODDR [...] cpan.org - Correspondence added

What OS is this? Also a perl -V might be helpful.

Thu Apr 08 17:09:25 2010 http://www.google.com/profiles/jbao605 - Correspondence added

Thanks. I will look into that. Are you aware if Net::OpenSSH allows one to capture the output and error separately, as well as the exit code? On Thu Apr 08 16:55:34 2010, TODDR wrote: Show quoted text

> I'm not saying this isn't a bug, but if the problem is only with ssh, > I'd encourage you to look at > Net::OpenSSH, which specifically focuses on interfacing with ssh. I've > found it very useful in the > past. > > Note that you must be interfacing with Open SSH in order for this to > work for you.

Thu Apr 08 17:17:55 2010 http://www.google.com/profiles/jbao605 - Correspondence added

From:

Bao, J

It is Sun OS 5.10, Perl 5.10 64bit. On Thu Apr 08 16:56:38 2010, TODDR wrote: Show quoted text

> What OS is this? Also a perl -V might be helpful.

Thu Apr 08 19:22:36 2010 TODDR [...] cpan.org - Correspondence added

On Thu Apr 08 17:09:25 2010, http://www.google.com/profiles/jbao605 wrote: Show quoted text

> Thanks. I will look into that. Are you aware if Net::OpenSSH allows > one to capture the output and error separately, as well as the exit code? >

Yep. IMO, it does way more than IPC::Run can when dealing with ssh

Mon Apr 19 11:15:55 2010 TODDR [...] cpan.org - Taken

Mon Apr 19 11:17:08 2010 TODDR [...] cpan.org - Correspondence added

Hi can you tell me if Net::OpenSSH fixed your problem? I plan to leave the ticket open, but It would be helpful to know down the road so we know if this is a viable alternative.

Tue Jun 28 23:19:42 2011 TODDR [...] cpan.org - Correspondence added

No solution but I released a dev release on another ticket and realized I never TODO'd this test when adding it originally.

Tue Jun 28 23:20:05 2011 TODDR [...] cpan.org - Status changed from 'open' to 'stalled'

Tue Jun 28 23:20:05 2011 TODDR [...] cpan.org - Severity Normal added

Fri Jul 01 00:38:44 2011 TODDR [...] cpan.org - Correspondence added

Net::OpenSSH is a much better solution than running ssh via IPC::Run. Resolving issue as not relevant to IPC::Run

Fri Jul 01 00:38:45 2011 The RT System itself - Status changed from 'stalled' to 'open'

Fri Jul 01 00:38:45 2011 TODDR [...] cpan.org - Status changed from 'open' to 'rejected'