All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Matthias Kestenholz <matthias@spinlock.ch>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] Documentation: git-daemon inetd configuration fix
Date: Fri, 16 Mar 2007 01:43:02 -0700	[thread overview]
Message-ID: <7vabydwpd5.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <11740316693552-git-send-email-matthias@spinlock.ch> (Matthias Kestenholz's message of "Fri, 16 Mar 2007 08:54:29 +0100")

Matthias Kestenholz <matthias@spinlock.ch> writes:

>  On my debian server, this change was needed to get git-daemon running.
>  I am no inetd expert, so I don't know where the error was.
>
>  Perhaps this patch might help someone else.
>
>
> diff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt
> index 9ddab71..499c1f3 100644
> --- a/Documentation/git-daemon.txt
> +++ b/Documentation/git-daemon.txt
> @@ -177,7 +177,7 @@ git-daemon as inetd server::
>  +
>  ------------------------------------------------
>  	git stream tcp nowait nobody  /usr/bin/git-daemon
> -		git-daemon --inetd --verbose --export-all
> +		/usr/bin/git-daemon --inetd --verbose --export-all
>  		/pub/foo /pub/bar
>  ------------------------------------------------

That sounds _very_ wrong.  What you changed is argv[0] (i.e. the
beginning of "service program arguments" field) and it should
not matter what you have there for inetd to launch git-daemon.
Presumably your inetd runs with /usr/bin in your path so even
the "service program" field (the one after 'nobody') should not
need the full path (but it is a good idea to be explicit in that
field as a principle), but needing the full path in argv[0]?

On _my_ debian box, I do not need a full path there, so it is
not even Debian in general but problem is on your particular
box.  Can you dig a bit more to see what you are doing any
differently?

For example, do you really mean the "service program arguments"
field that matters?

One plausible mistake scenario you _could_ have made is
something like this.  You compile git yourself and install it in
/home/matt/bin/git-daemon, and you needed to spell that path out
in "service program" field, but you found it out by trial and
error, and during that experiment you did not change "service
program" field (which actually matters) but "service program
arguments" field first.  And the working configuration you
happened to end up with was like this:

	git stream tcp nowait nobody /home/matt/bin/git-daemon \
        	/home/matt/bin/git-daemon --inetd ...

and then you tried to generalize it like this:

	git stream tcp nowait nobody /usr/bin/git-daemon \
        	/usr/bin/git-daemon --inetd ...

For one thing, I just tried to make sure argv[0] does not matter
at all by having this entry in my inetd.conf:

	git stream tcp nowait nobody /git/bin/git-daemon \
        	foobla --inetd ...

/git/bin is where I installed my git.  If I replace foobla with
anything else, it responds just fine.

  reply	other threads:[~2007-03-16  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16  7:54 [PATCH/RFC] Documentation: git-daemon inetd configuration fix Matthias Kestenholz
2007-03-16  8:43 ` Junio C Hamano [this message]
2007-03-16  9:02   ` Matthias Kestenholz

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=7vabydwpd5.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=matthias@spinlock.ch \
    /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.