Re: Issue #2580 revisited: Windows unclean TCP close [SEVERE]

Branko --

I did some research and I don't think a windows-to-windows test is going to mean
much. The problem manifests itself over svn+ssh, and I need an sshd for windows.

http://www.openssh.com/windows.html

They're all clients, not receiver daemons. The only one I could find that looks
remotely usable is freeSSHD

http://www.freesshd.com/?ctt=overview

and it's not something like a forking daemon. It's not listed on the OpenSSH
page either (of course). OpenSSH for Windows, also not listed, says things like
"coming soon, new developer..." the last one was in 2004 and the guy abandoned it.

I think virtually everyone on Windows who is using svn+ssh is working with a
Linux back end like me. Without the patch, it is unusable on a fast system with
a modest net connection, as I explained previously.

KILL_ONCE makes sense on Linux where it actually works. KILL_NEVER is the best
of a bad set of choices on Windows. Thanks for the encouragement. I really did
put a lot of time into this, much of up climbing multiple learning curves :-))

  -- Bob

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2408617
Received on 2009-10-18 10:19:21 CEST