Linus Torvalds wrote:
On Fri, 16 Jun 2006, Goo GGooo wrote:
quoted
I suggest adding SO_KEEPALIVE option on the git socket.
Actually, the really irritating thing is that we actually generate all
these nice status updates, which just makes pulling and cloning a lot more
comfortable, because you actually see what is going on, and what to
expect.
Except they only work over ssh, where we have a separate channel (for
stderr), and with the native git protocol all that nice status work just
gets flushed to /dev/null :(
OpenBSD has CVS access to their repos over SSH even for anonymous users.
Could something similar be set up on git.kernel.org as well?
And in your case, the usability downside actually turned into a real
accessibility bug.
Same issue here. Thanks for the hint. Attached is a patch against git
1.4.0 that solves it perfectly in my case.
Sysctl settings (for keepalive every 10 sec):
net.ipv4.tcp_keepalive_intvl=10
net.ipv4.tcp_keepalive_time=10
Michal