Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Limitation in SCP? Date: Mon, 13 Dec 2004 15:50:27 -0500 References: <20041213143745.28b476b5@boing.blorch.org> From: Francis Litterio X-Random-Quote: It requires a very unusual mind to undertake the analysis of the obvious. -- Alfred North Whitehead (1861 - 1947) In-Reply-To: <20041213143745.28b476b5@boing.blorch.org> (Bob Smart's message of "Mon, 13 Dec 2004 14:37:45 -0600") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Bob Smart wrote: > 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 seen the same thing, except I see scp stop transferring data _very_ close to the end of the large file (i.e., within 10000 bytes of the end). I've only seen this when scp'ing files that are over 100 MB. I've found that this equivalent command works when scp fails: ssh remotehost cat remotefile > localfile > I've only seen this when copying between two W2K machines In my case it's only between two XP machines. -- Francis Litterio franl@world.std.com http://world.std.com/~franl/ GPG and PGP public keys available on keyservers. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/