2011/6/20 Konstantin Khomoutov <flatw...@users.sourceforge.net>:
> On Mon, Jun 20, 2011 at 02:17:44PM -0300, Vinicius Massuchetto wrote:
> [...]
>> >> I'm currently restarting services with the `sv start/stop` command
>> >> line, and killing service process to ensure it got reloaded.
>> > I don't understand the meaning of this sentence--are you claiming that
>> > restarting the git-daemon service fixes the problem?
>> > Does it fixe the problem temporarily?  Does not fix it at all?
>> No. It doesn't fix anything. Sorry for not saying that my
>> understanding of this syslog error is that another git-daemon instance
>> is already running on port 9418, as netstat says. That's why I tried
>> to kill it.
>> 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.

> 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* LISTEN 23528/git-daemon
tcp6 0 0 :::9418 :::* LISTEN 23528/git-daemon

> [...]
>> > 2) Try running git-daemon from inetd.  Note that in order for this to
>> >   work you surely should not have the daemon running.
>> You got any suggested link or configuration set for this?
> The "EXAMPLES" section of the git-daemon man page contains exactly the
> line which should work OK with openbsd-inetd which is the default inetd
> implementation in Debian IIRC.
> You just paste that line to /etc/inetd.conf and do
> # invoke-rc.d openbsd-inetd restart

I'll check it out. Thanks!

Vinicius Massuchetto

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 git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to