Hi Jeff, I think I found the explanation why v1.5.3.6 works for me (and others apparently) but master and next don't. The fairly recent changes to the PATH handling in exec_cmd.c done by Scott R Parish <srp@xxxxxxxxxxxx>, I believe, didn't make it into maint. Adjusting the PATH git-daemon sees is fixing my problem even in master and next. Thanks for your help and time. Cheers, Emil. > -----Original Message----- > From: Jeff King [mailto:peff@xxxxxxxx] > Sent: Tuesday, November 20, 2007 12:26 PM > To: Medve Emilian > Cc: git@xxxxxxxxxxxxxxx > Subject: Re: git-daemon > > On Tue, Nov 20, 2007 at 09:54:13AM -0700, Medve Emilian wrote: > > > I just built and installed the latest master (and next) and > then I tried > > to clone (as I usualy do) one of my repositories. I run > git-daemon only > > with the upload-pack service enabled. > > [...] > > > > Nov 20 10:17:04 emmedve1-12 git-daemon: [3921] Connection from > > 10.82.124.104:2978 > > Nov 20 10:17:04 emmedve1-12 git-daemon: [3921] Extended > attributes (18 > > bytes) exist <host=server> > > Nov 20 10:17:04 emmedve1-12 git-daemon: [3921] Request > upload-pack for > > '/srv/scm/linux-2.6.git' > > I don't see anything useful there. Have you tried running git-daemon > with --verbose? If that doesn't turn up anything, can you try running > with GIT_TRACE=1 to see the upload pack command that is being executed > (and try running it yourself)? > > > Did you try this and is working for you? > > Yes, it works fine (though I ran it under tcpserver, not xinetd). > > -Peff - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html