[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Bob Denny <rdenny_at_dc3.com>
Date: Thu, 22 Oct 2009 05:56:27 -0700 (PDT)

> (I'm not going to commit the patch myself simply because I cannot test
> it since I don't have a Windows machine. And I'd rather see the effects
> of what I commit with my own eyes.)

I hope someone will validate it and either apply the patch or come up with a "better" way to solve the problem. As it is now, (1.6.6) svn cannot be used via svn+ssh (and probably other tunnels) under the conditions I outlined.

> The default action for SIGHUP is terminating the process.
> I don't see anything in the svnserve source code overriding SIGHUP.

The problem is that sshd is waiting for ITS protocol (SSH) to complete before things wind down. Maybe the other end (the client) has more data to send? Since the client didn't initiate the SSH closing phase (due to it having been instantly killed) things at the server are in an indeterminate state, and eventually (many minutes later) the chain of processes on the server exit through error paths.

  -- Bob

Received on 2009-10-22 14:56:35 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.