From: Deskin Miller <deskinm@umich.edu>
To: Gary Yang <garyyang6@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: Challenge of setting up git server (repository). Please help!
Date: Thu, 20 Nov 2008 18:08:59 -0500 [thread overview]
Message-ID: <20081120230859.GA13683@euler> (raw)
In-Reply-To: <146002.93100.qm@web37908.mail.mud.yahoo.com>
On Thu, Nov 20, 2008 at 02:43:30PM -0800, Gary Yang wrote:
> Many thanks for your explanation. I hope I understand what you said. I deleted /etc/xinetd.d/git-daemon. Then, I tried to git pull. But, I got connection refused. git uses port 9418. Should I request IT Admin to open the port 9418 for me?
You'll need port 9418 open, yes; but since it's an unprivileged port (1024 or
higher), you can use it as a regular user and don't need IT intervention unless you have some firewall set up which they need to override for you.
> git pull git://git.mycompany.com/pub/git/u-boot.git HEAD
> git.mycompany.com[0: 10.66.4.168]: errno=Connection refused
> fatal: unable to connect a socket (Connection refused)
It's possible, and likely simpler, to use git-daemon directly, instead of
having it be managed by inetd; especially for initial debugging, I'd recommend
getting that working before trying to determine if you're having issues with
inetd configuration: to do so, just run git-daemon with all the same arguments
except for --inetd.
You said you deleted the xinetd config, but that's only relevant if your
machine actually uses inetd as its super-server. You should do 'ps -A | grep
inetd' (which will match either inetd or xinetd), and see which one is running.
If it's inetd, you should be all set, and the issue doesn't look like inetd
(assuming you sent it a signal to reload its config file). If on the other
hand xinetd is running, you need to use the xinetd config file, and fix the
server_args to look like the arguments which exist in the inetd file. Again,
you need to signal xinetd at this point to reload its configuration.
Based on the linux kernel version you're reporting, I'm guessing you have some
sort of Red Hat based system, which uses xinetd to the best of my knowledge.
> Another question, I got no output of "netstat | grep 9418". It means no program runs at port 9418 at the public repository machine. Is it correct?
>
> netstat | grep 9418
netstat translates IP addresses to dns names, and ports to service names by
default; so, given the line listed in /etc/services, this will show
'0.0.0.0:git' or something. Also, it lists established connections, not
listening sockets, by default. I'd recommend spending some time with the man
page if you're going to use it to debug your setup.
Deskin Miller
next prev parent reply other threads:[~2008-11-20 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 21:39 Challenge of setting up git server (repository). Please help! Gary Yang
2008-11-20 22:04 ` Asheesh Laroia
2008-11-20 22:13 ` Deskin Miller
2008-11-20 22:43 ` Gary Yang
2008-11-20 23:08 ` Deskin Miller [this message]
2008-11-20 23:48 ` Gary Yang
2008-11-20 23:54 ` Gary Yang
2008-11-20 23:59 ` J.H.
2008-11-21 0:12 ` Gary Yang
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 0:14 Gary Yang
2008-11-21 0:39 ` Gary Yang
2008-11-21 7:22 ` Mike Galbraith
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=20081120230859.GA13683@euler \
--to=deskinm@umich.edu \
--cc=garyyang6@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox