Re: svn+ssh leaves sshd and svnserve processes running
Bob Denny wrote:
>> Doesn't the OS still close the connection?
> No. It must happen in the TCP stack within the process. If the process is gone, the only thing the oS does is send RST (reset) packets back to the other end.
> Here's what I posted to the subversion-dev group. It affects Tortoise because Tortoise uses the Subversion libraries:
> Subj: Issue #2580 revisited: Windows unclean TCP close [SEVERE]
> SVN 1.6.5 on Windows and using svn+ssh fails to properly complete and close the TCP connection. leaving the remote sshd/svnserve processes running (CentOS Linux server). These last "forever", accumulating until the sysop disables your SSH access :-) This is a severe problem. It doesn't always appear on slower CPUs with fast connections to the remote svn+ssh repo. However, my system is a 2.6GHz quadcore, and the remote repo is across the public Internet. This is the worst case environment as you'll see. I am certain this problem is not unique to me.
Hmmm... I wonder if this is related to me seeing Subversion leave half
open TCP connections for every svn:external done during an svn
update/checkout on Windows. Similar to issue #1448. However, these
connections are terminated when the process completes when using the
http:// protocol, but will cause an update to hang on Windows XP when
you try an update hundreds of externals...
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-16 02:24:00 CEST
This is an archived mail posted to the TortoiseSVN Dev