From: Jonathan Nieder <jrnieder@gmail.com>
To: John Griessen <john@ecosensory.com>
Cc: git@vger.kernel.org
Subject: Re: git-daemon serving repos with repo.git/git-daemon-export-ok
Date: Mon, 3 Jan 2011 17:55:01 -0600 [thread overview]
Message-ID: <20110103235501.GA32262@burratino> (raw)
In-Reply-To: <4D225DFA.50805@ecosensory.com>
John Griessen wrote:
> git version 1.7.2.3
Good.
> vking@mail:/etc/sv$ sv stat git-daemon
> fail: git-daemon: unable to change to service directory: file does not exist
Ah, you switched to running git daemon directly.
> I can push to these repos with gitosis, and the permissions are:
>
> vking@mail:/srv/gitosis/repositories$ ll
> total 16
> drwxr-xr-x 7 gitosis gitosis 4096 Dec 30 12:32 extrudator.data.git
So the gitdaemon user (used by git-daemon-run) wouldn't be able to
access them.
> vking@mail:/etc/sv$ cat strace.out
> execve("/usr/lib/git-core/git-daemon",
> ["/usr/lib/git-core/git-daemon", "--verbose", "--strict-paths",
> "--user=git", "--group=gitosis", "/srv/gitosis/repositories"], [/*
> 10 vars */]) = 0
In this case simple --verbose output would probably be more useful.
(That's what cat-ing /var/log/git-daemon/current would have given
if git-daemon-run were still installed.)
Thanks for the strace. I should have mentioned that strace -f can
help by following child processes, though that doesn't seem to be
an issue here. It looks like another git-daemon process is running at
the same time? (One can check with "netstat -t -a".)
next prev parent reply other threads:[~2011-01-03 23:55 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 ` git-daemon serving repos with repo.git/git-daemon-export-ok John Griessen
2011-01-03 22:47 ` John Griessen
2011-01-03 23:11 ` Jonathan Nieder
2011-01-03 23:38 ` John Griessen
2011-01-03 23:55 ` Jonathan Nieder [this message]
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=20110103235501.GA32262@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@ecosensory.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 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).