git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: skillzero@gmail.com
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: git clone failing over slow links?
Date: Tue, 9 Jun 2009 12:58:57 -0700	[thread overview]
Message-ID: <2729632a0906091258v7ec334faue725c71bdd11165c@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0906091443050.31536@xanadu.home>

On Tue, Jun 9, 2009 at 11:55 AM, Nicolas Pitre<nico@cam.org> wrote:
>
> Do you clearly have a set of people for whom the clone works and another
> set with issues?

Yes. Several us are able to reliably clone every time. A few users are
able to clone once or twice (maybe 1 out of every 10 times), but
otherwise, it fails when the server drops the connection.

From what they said, it looked like read_in_full() (in wrapper.c)
isn't getting a full buffer. In two cases, 4077 or 4082 out of 4097
bytes. xread is returning 0 as you'd expect for an EOF.

> 147 KiB/s is not particularly slow either.  What is fast enough for the
> clone to usually succeed?

Mine is 500 KB/sec where it always succeeds. I can try using dummynet
to simulate a slow link though.

> Also, since this is through an ssh connection, do you have anything in
> your syslog from sshd (usually in /var/log/secure) about anything
> unusual for the connection to go down?

I'm trying to get that from the server admin now.

      reply	other threads:[~2009-06-09 19:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 15:52 git clone failing over slow links? skillzero
2009-06-09 17:12 ` Robin H. Johnson
2009-06-09 18:42   ` Nicolas Pitre
2009-06-09 18:49     ` Robin H. Johnson
2009-06-09 18:55 ` Nicolas Pitre
2009-06-09 19:58   ` skillzero [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=2729632a0906091258v7ec334faue725c71bdd11165c@mail.gmail.com \
    --to=skillzero@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).