git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Erez Zilber" <erezzi.list@gmail.com>
To: "Robert Haines" <rhaines@manchester.ac.uk>
Cc: "Matthias Kestenholz" <mk@spinlock.ch>, git@vger.kernel.org
Subject: Re: git-clone works with ssh but not with http/https/git
Date: Tue, 24 Jun 2008 17:45:07 +0300	[thread overview]
Message-ID: <ce513bcc0806240745l365b2d22ga007deb01a93e4b6@mail.gmail.com> (raw)
In-Reply-To: <BC8F2A2A-9817-401B-BAC3-F36ED42976E5@manchester.ac.uk>

On Tue, Jun 24, 2008 at 5:08 PM, Robert Haines <rhaines@manchester.ac.uk> wrote:
>>> So your clone address for git:// is wrong, you don't need the /pub/git:
>>> git clone git://erez.zilber@kites/erez.zilber/my_test.git
>>> As you've moved the root of the filesystem as far as git-daemon is
>>> concerned
>>> to /pub/git with the --base-path option.
>>
>> I understand. However, when I try to run it according to your suggestion:
>>
>> [root@kd001 t]# git clone git://erez.zilber@kites/erez.zilber/my_test.git
>> Initialized empty Git repository in
>> /home/erez.zilber/work/tmp/t/my_test/.git/
>> fatal: Unable to look up erez.zilber@kites (port 9418) (Name or
>> service not known)
>> fetch-pack from 'git://erez.zilber@kites/erez.zilber/my_test.git' failed.
>
> That error is saying that the name of the service is wrong, so you're right
> to do it without the "erez.zilber@" bit.
>
>> I also tried to run it without "erez.zilber@":
>>
>> [root@kd001 t]# git clone git://kites/erez.zilber/my_test.git
>> Initialized empty Git repository in
>> /home/erez.zilber/work/tmp/t/my_test/.git/
>> kites[0: 172.16.1.11]: errno=Connection refused
>> fatal: unable to connect a socket (Connection refused)
>> fetch-pack from 'git://kites/erez.zilber/my_test.git' failed.
>
> This looks like that either there is nothing listening (if you're running
> though xinetd have you restarted it? And have you added the right bits to
> /etc/services?) or there's a firewall in the way... git defaults to 9418 so
> check that it's open.

The problem was that it listened to requests coming from the local
machine. Now (after fixing that), everything seems to work. Thanks for
the help.

BTW - I'm currently running git-daemon in the following way:

sudo git-daemon --base-path=/pub/git/ --export-all

Is there any advantage to run it through xinetd? How do you run it?

Thanks,
Erez

  reply	other threads:[~2008-06-24 14:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 11:15 git-clone works with ssh but not with http/https/git Erez Zilber
2008-06-24 11:21 ` Matthias Kestenholz
2008-06-24 11:45   ` Erez Zilber
2008-06-24 11:48     ` Johannes Schindelin
2008-06-24 12:07       ` Erez Zilber
2008-06-24 12:25         ` Jakub Narebski
2008-06-24 13:42           ` Erez Zilber
2008-06-24 13:54             ` Anton Gladkov
2008-06-24 13:59               ` Anton Gladkov
2008-06-24 14:02                 ` Matthias Kestenholz
2008-06-24 14:16               ` Erez Zilber
2008-06-24 18:58               ` Jakub Narebski
2008-06-24 14:05             ` Matthieu Moy
2008-06-24 12:41         ` Johannes Sixt
2008-06-24 12:35     ` Robert Haines
2008-06-24 13:53       ` Erez Zilber
2008-06-24 14:08         ` Robert Haines
2008-06-24 14:45           ` Erez Zilber [this message]
2008-06-24 17:10             ` Daniel Barkalow
2008-06-25  6:56               ` Erez Zilber

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=ce513bcc0806240745l365b2d22ga007deb01a93e4b6@mail.gmail.com \
    --to=erezzi.list@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mk@spinlock.ch \
    --cc=rhaines@manchester.ac.uk \
    /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).