This is the mail archive of the
mailing list for the Cygwin project.
Limitation in SCP?
- From: Bob Smart <bsmart at blorch dot org>
- To: cygwin at cygwin dot com
- Date: Mon, 13 Dec 2004 14:37:45 -0600
- Subject: Limitation in SCP?
- Organization: Blorch!
I've discovered that in some circumstances, scp seems to get tired early when transferring a largish file (around 200MB). It copies diligently for the first 20-40MB (exactly where it stops varies from run to run), then CPU usage drops to zero, the file stops growing on the receiving end, there's no apparent network traffic, and everything just pretty much halts. A ps shows the scp task running, but not doing anything.
I've only seen this when copying between two W2K machines (both Cygwin, both using the Cygwin SSH package, both of pretty recent vintage with DLL 1.5.11). I did my development testing between Linux and NT, and I never saw this behavior in that environment. It always fails with the W2K machines.
I also never see this happen with tar. If I do a tar-to-tar pipe via SSH, everything works even in the W2K-to-W2K environment. However, I'd like to understand why I can't use scp for this.
GPG public key <email@example.com> available from public key server
network or from www.blorch.org/bob
Fingerprint BA4A 552C BE3D 8C40 ED76 F372 DF9E 320D 37FA 16AC
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html