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

RE: Re: svn+ssh leaves sshd and svnserve processes running

From: Bob Denny <rdenny_at_dc3.com>
Date: Wed, 14 Oct 2009 16:36:13 -0700 (PDT)

Mike --

I've read through the references you gave in detail, plus tested more here, and the problem is exactly the one that's mentioned for 1.6.0 or later! I didn't even know what SVN was three weeks ago :-) I have gone back (using the current TortoisePLink sources from the TortoiseSVN trunk!!) and confirmed that the instant that PLink sends the last packet back to svn.exe, PLink vaporizes, not getting a chance to complete the converstaion with the remote sshd/svnserve, even yanking down the socket so fast that the remote end gets a TCP RST packet. So after all I was on the right scent, I just got seduced by the sources, learning how PLink works :-)

Thank you again for the references. I now know exactly what's going on. In the case of Windows, there's no SIGKILL signal, I'm guessing that svn.exe (and TortoiseProc!) are killing their children outright, which is why things are left in a screwed up state on the remote end. I'm going to post this on the dev list now. This is end of my posting here (unless I find some sort of a solution). I'm going to have a look at the TortoiseProc sources to see what I''m dealing with :-)


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-15 01:36:10 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.