On Mon, Jun 20, 2011 at 05:04:12PM -0300, Vinicius Massuchetto wrote:
> >> So, both of these actions will log this message into syslog:
> >> $sv stop git-daemon; sv start git-daemon
> >> $kill -9 <git daemon pids>
> > So you mean if you kill -9 the git-daemon and then `sv start` it, it
> > logs the above message to syslog (that it can't bind to a socket)?
> If I kill it, I don't even need to `sv start` it. The system will
> persist in getting it up again.
Presumably, that is the expected behaviour of runit, which
> > And then you can see it working (`netstat -ntlp`) but can't clone even
> > though it appears to listen?
> Yes. It appears to be listening properly. Here's the output of
> `netstat -ntlp | grep git`:
> tcp 0 0 0.0.0.0:9418 0.0.0.0:* LISTEN 23528/git-daemon
> tcp6 0 0 :::9418 :::* LISTEN 23528/git-daemon
Hmm, so it listens.
Now what is the error git on a client machine shows you when you're
trying to clone?
May it be that the repo you're trying to clone is not located in a
directory git-daemon expects it to be located in?
Or that the credentials possessed by the running git-daemon instance are
insufficient to access the said repository?
Or did you forget to `touch git-daemon-export-ok` file in that repo?
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at