My @files contains 6 filenames, and the output that segment produces is:for(@files) { $ret = $ssh2->scp_get("$dir/$_", "$_"); print "RET: $ret\n"; }
I'm thinking it's the Net::SSH2::Channel::DESTROY that occurs between successive scp_get() calls that might be critical. I'm using Net-SSH2-0.19 (built against libssh2-1.0).libssh2_scp_recv(ss->session, path, &st) -> 0x3dae38c Net::SSH2::Channel::read(size = 506, ext = 0) - read 506 bytes - read 506 total Net::SSH2::Channel::read(size = 1, ext = 0) - read 1 bytes - read 1 total Net::SSH2::Channel::DESTROY RET: 1 libssh2_scp_recv(ss->session, path, &st) -> 0x3dae38c Net::SSH2::Channel::read(size = 500, ext = 0) - read 500 bytes - read 500 total Net::SSH2::Channel::read(size = 1, ext = 0) - read 1 bytes - read 1 total Net::SSH2::Channel::DESTROY RET: 1 libssh2_scp_recv(ss->session, path, &st) -> 0x3dae38c Net::SSH2::Channel::read(size = 499, ext = 0) - read 499 bytes - read 499 total Net::SSH2::Channel::read(size = 1, ext = 0) - read 1 bytes - read 1 total Net::SSH2::Channel::DESTROY RET: 1 libssh2_scp_recv(ss->session, path, &st) -> 0x3dae38c Net::SSH2::Channel::read(size = 507, ext = 0) - read 507 bytes - read 507 total Net::SSH2::Channel::read(size = 1, ext = 0) - read 1 bytes - read 1 total Net::SSH2::Channel::DESTROY RET: 1 libssh2_scp_recv(ss->session, path, &st) -> 0x3dae38c Net::SSH2::Channel::read(size = 570, ext = 0) - read 570 bytes - read 570 total Net::SSH2::Channel::read(size = 1, ext = 0) - read 1 bytes - read 1 total Net::SSH2::Channel::DESTROY RET: 1 libssh2_scp_recv(ss->session, path, &st) -> 0x3dae38c Net::SSH2::Channel::read(size = 493, ext = 0) - read 493 bytes - read 493 total Net::SSH2::Channel::read(size = 1, ext = 0) - read 1 bytes - read 1 total Net::SSH2::Channel::DESTROY RET: 1
In reply to Re: Net::SSH2 fails under heavy load
by syphilis
in thread Net::SSH2 fails under heavy load
by FloydATC
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |