git-daemon serving repos with repo.git/git-daemon-export-ok
- From
John Griessen <john@ecosensory.com>
- Date
- Jan 3, 2011, 21:49 UTC
- Message-ID
- <4D224475.1090805@ecosensory.com>
- In-Reply-To
- <S1751603Ab1ACU6e/20110103205834Z+1762@vger.kernel.org>
I would like to serving repos with repo.git/git-daemon-export-ok from a debian linux server installation, but I am getting symptoms of clone failing.
john@toolbench:~/EEProjects/test$ git clone git://ecosensory.com/tek_7k_ext.git Cloning into tek_7k_ext... fatal: protocol error: bad line length character: fata
I've read that that is due to the shell at the client end putting out extra characters... but other testers on other machines get it the same way...
Next I tried changing my command that runs git-daemon from
exec 2>&1 echo 'git-daemon starting.' exec chpst -ugitdaemon \ "$(git --exec-path)"/git-daemon --verbose --base-path=/var/cache /var/cache/git
to
exec 2>&1 echo 'git-daemon starting.' exec chpst -ugitdaemon \ "$(git --exec-path)"/git-daemon --verbose --base-path=/srv/gitosis /srv/gitosis/repositories
and results are:
john@toolbench:~/EEProjects/test$ git clone git://ecosensory.com/tek_7k_ext.git Cloning into tek_7k_ext... fatal: protocol error: bad line length character: fata john@toolbench:~/EEProjects/test$ git clone git://ecosensory.com/repositories/tek_7k_ext.git Cloning into tek_7k_ext... fatal: protocol error: bad line length character: fata
What can I do to simplify this testing and pin point the problem?
Or is gitweb recommended?
thanks,
John Griessen