From: Holger Freyther <zecke@selfish.org>
To: git@vger.kernel.org
Subject: Re: Unable to clone via git protocol / early EOF / index-pack failed
Date: Sat, 26 Mar 2011 17:34:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20110326T183100-349@post.gmane.org> (raw)
In-Reply-To: loom.20110326T180713-801@post.gmane.org
Holger Freyther <zecke <at> selfish.org> writes:
> It is a bit difficult to track all the processes that get started and what they
> should do and to figure out at which point the fd for the tcp socket is really
> closed.
If I do the below hack it is working fine. Adding a fflush(NULL).. or a
close(fileno(stdout)).. fsync... sched_yield() is not fixing it though.
diff --git a/upload-pack.c b/upload-pack.c
index 72aa661..4cd12c9 100644
--- a/upload-pack.c
+++ b/upload-pack.c
@@ -695,6 +695,8 @@ static void upload_pack(void)
get_common_commits();
create_pack_file();
}
+
+ sleep(1);
}
int main(int argc, char **argv)
next prev parent reply other threads:[~2011-03-26 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 10:27 Unable to clone via git protocol / early EOF / index-pack failed Harald Welte
2011-03-24 10:30 ` Harald Welte
2011-03-26 17:12 ` Holger Freyther
2011-03-26 17:34 ` Holger Freyther [this message]
2011-03-26 17:58 ` Matthieu Moy
2011-03-26 18:50 ` Holger Freyther
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=loom.20110326T183100-349@post.gmane.org \
--to=zecke@selfish.org \
--cc=git@vger.kernel.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.
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).