From: John Griessen <john@ecosensory.com>
To: git@vger.kernel.org
Subject: git-daemon serving repos with repo.git/git-daemon-export-ok
Date: Mon, 03 Jan 2011 15:49:41 -0600 [thread overview]
Message-ID: <4D224475.1090805@ecosensory.com> (raw)
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
next parent reply other threads:[~2011-01-03 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1751603Ab1ACU6e/20110103205834Z+1762@vger.kernel.org>
2011-01-03 21:49 ` John Griessen [this message]
2011-01-03 22:47 ` git-daemon serving repos with repo.git/git-daemon-export-ok John Griessen
2011-01-03 23:11 ` Jonathan Nieder
2011-01-03 23:38 ` John Griessen
2011-01-03 23:55 ` Jonathan Nieder
2011-01-04 1:58 ` John Griessen
2011-01-04 2:11 ` Jonathan Nieder
2011-01-04 3:09 ` Jonathan Nieder
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=4D224475.1090805@ecosensory.com \
--to=john@ecosensory.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.