From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Re: http protocol, cloning git.git, fails (too many open files)
Date: Sat, 12 Nov 2005 15:21:45 -0800 [thread overview]
Message-ID: <7vmzk9e9km.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <86acg9ijwa.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "12 Nov 2005 14:25:09 -0800")
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> $ mkdir foo
> $ cd foo
> $ cg-clone http://www.kernel.org/pub/scm/git/git.git git.new
> Fetching head...
> Fetching objects...
> progress: 1 objects, 191 bytes
> progress: 2 objects, 519 bytes
> progress: 3 objects, 5851 bytes
> progress: 4 objects, 7671 bytes
>...
>
> progress: 66 objects, 187452 bytes
>
> And at this point, it hung. I had to ^C.
This sounds like the problem the patch Pasky posted last night
addresses.
However, one thing puzzles me. I just tried to reproduce it by
doing this:
$ rm -fr git-http
$ ulimit -n 16
$ git clone http://www.kernel.org/pub/scm/git/git.git git-http
and it did not fail on my Linux box. This is from the tip of
the master tree (essentially the same as 0.99.9h aka 1.0rc1),
built without Pasky's patch. Maybe the number of in-transit
requests in your case is much higher with your connection while
waiting for a packfile to arrive than my setup.
Could you please try with the patch Nick posted (which covers
less) and then with Pasky's patch?
next prev parent reply other threads:[~2005-11-12 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 22:25 http protocol, cloning git.git, fails (too many open files) Randal L. Schwartz
2005-11-12 23:21 ` Junio C Hamano [this message]
2005-11-14 0:01 ` walt
2005-11-14 0:42 ` wa1ter
2005-11-14 1:09 ` Petr Baudis
2005-11-14 1:52 ` Junio C Hamano
2005-11-14 13:09 ` wa1ter
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=7vmzk9e9km.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.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 NNTP newsgroup(s).