public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [1.7] regression wrt scp?
Date: Thu, 08 Jan 2009 16:36:00 -0000	[thread overview]
Message-ID: <20090108161513.GA10914@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20090108103349.GB14304@calimero.vinschen.de>

On Thu, Jan 08, 2009 at 11:33:49AM +0100, Corinna Vinschen wrote:
>On Jan  7 00:52, Charles Wilson wrote:
>> With cygwin-1.7.36:
>> 
>> $ scp gcc-tools-autoconf-2.59-10-src.tar.bz2 sources.redhat.com:
>> gcc-tools-autoconf-2.59-10-src.tar.bz2 100%  911KB  60.8KB/s   00:15
>> 
>> With cygwin-1.7.37:
>> 
>> $ scp gcc-tools-autoconf-2.59-10-src.tar.bz2 sources.redhat.com:
>> gcc-tools-autoconf-2.59-10-src.tar.bz2  21%  192KB  91.8KB/s - stalled -
>> gcc-tools-autoconf-2.59-10-src.tar.bz2: Broken pipe
>> 
>> and has to be killed with CTRL-C. ssh works fine in both cases.
>> 
>> Is anybody else seeing this?
>
>I could reproduce it with Cygwin from CVS as well.  It did not occur
>over a fast LAN connection, but it occurs reliably over my much slower
>ADSL connection when trying to upload to sourceware.  The strace didn't
>exactly enlighten me yet.  That's Chris' code and I'm not very familar
>with it.

It's already on my list to investigate.  When I saw "broken pipe" I
thought it could be something in the new pipe code.

cgf

--
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/

  reply	other threads:[~2009-01-08 16:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07  8:19 Charles Wilson
2009-01-08 11:29 ` Corinna Vinschen
2009-01-08 16:36   ` Christopher Faylor [this message]
2009-01-08 16:41     ` Corinna Vinschen
2009-01-26 10:52     ` Christopher Faylor
2009-01-26 15:46       ` Corinna Vinschen
2009-01-26 17:17         ` Christopher Faylor
2009-01-26 18:59           ` Corinna Vinschen
2009-01-26 21:35             ` Christopher Faylor
2009-01-26 19:46           ` Corinna Vinschen
2009-01-27 19:33           ` Christopher Faylor
2009-01-28  3:01             ` Charles Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090108161513.GA10914@trixie.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).