From: Adam Piatyszek <ediap@users.sourceforge.net>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Wincent Colaiuta <win@wincent.com>,
Junio C Hamano <gitster@pobox.com>,
git mailing list <git@vger.kernel.org>,
srp@srparish.netq
Subject: Re: git-daemon breakage in 1.5.4
Date: Wed, 06 Feb 2008 13:02:00 +0100 [thread overview]
Message-ID: <47A9A1B8.5090501@users.sourceforge.net> (raw)
In-Reply-To: <47A98092.2070509@viscovery.net>
* Johannes Sixt [6 II 2008 10:40]:
> When I run git-daemon with a reduced path similar to this:
>
> PATH=/bin:/usr/bin /usr/local/bin/git-daemon ...
>
> i.e. git is installed in /usr/local/bin, but it is not in PATH, then I
> also get "hung up unexpectedly" from a client that connects to this server.
>
> Which makes me think that you xinetd doesn't pass a PATH to git-daemon
> that includes /usr/local/bin. Add this to your /etc/xinetd.d/git:
>
> env = PATH=/bin:/usr/bin:/usr/local/bin
You can also run "git daemon" passing --exec-path as a git argument.
This should help. For instance, I use the following configuration in
inetd.conf (SunOS 5.9):
git stream tcp nowait gituser /usr/local/bin/git \
git --exec-path=/usr/local/bin daemon --inetd \
--base-path=/export/home/gituser/git /export/home/gituser/git
BR,
/Adam
--
.:. Adam Piatyszek (ediap) .:.....................................:.
.:. ediap@users.sourceforge.net .:................................:.
prev parent reply other threads:[~2008-02-06 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 15:39 git-daemon breakage in 1.5.4 Wincent Colaiuta
2008-02-05 17:49 ` Scott Parish
2008-02-05 19:28 ` Wincent Colaiuta
2008-02-05 20:02 ` Junio C Hamano
2008-02-06 8:05 ` Wincent Colaiuta
2008-02-06 8:46 ` Junio C Hamano
2008-02-06 9:44 ` Wincent Colaiuta
2008-02-06 9:40 ` Johannes Sixt
2008-02-06 10:12 ` Wincent Colaiuta
2008-02-06 10:28 ` Johannes Sixt
2008-02-06 11:39 ` Wincent Colaiuta
2008-02-06 11:33 ` Johannes Sixt
2008-02-06 12:02 ` Adam Piatyszek [this message]
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=47A9A1B8.5090501@users.sourceforge.net \
--to=ediap@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=srp@srparish.netq \
--cc=win@wincent.com \
/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.