On Tue, 7 Nov 2006, Gisle Vanem wrote:

> Just playing around with scp, I find curl now sucks up 100% CPU time while
> waiting for the server to respond at port 22. I'm not even sure the server
> listens at port 22.

Can you check? Because if it doesn't even listen on 22, the SCP code shouldn't
even get involved and it would be a plain libcurl bug. I would guess that it
does connect and that libssh2 starts to play...

> Where is the time spent? In libcurl or libssh2?

I say in libssh2, but I'm not sure. It could also be a bug in the libcurl <=>
libssh2 integration that causes this. Can you try digging a little deeper? The
Curl_scp_recv() function, called from within Curl_read() should be a fair
starting-point...

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html