"Steve Williams" <stevewilliams@kromestudios.com> writes:
> I'm trying to get svn+ssh working on Win32 after having so many problems
> with the http access protocol. Yet another timeout on a large commit that
> corrupted the repository. http-compression set to "no". An attempt to
> checkout a new working copy after the timeout on commit resulted in half a
> working copy before getting a chunk read error.
I sure wish we had a way to reproduce your commit timeout problems.
You claim http-compression is "no", but IIRC, your win32 client may or
may not have been reading your registry or config-file. Did you ever
figure out how to ensure that mod_deflate was totally deactivated on
the server-side? The fact that you get a timeout *at all* indicates
to me that the server is still buffering a compressed repsonse.
And what do you mean by "timeout on a large commit corrupted the
repository"? You mean, you had to run 'svnadmin recover'? That
shouldn't happen. If the client MERGE repsonse timed out, it means
the commit succeeded, but the working copy was never notified. But
there should be any repository recovery problems. (If there are, then
that's a whole new topic to discuss.)
As for the checkout -- "chunk read error"? Never even heard of that
error... from anyone, actually, ever. I'd like to hear more about it.
> On Linux this command works fine. On Win32 this command just waits around
> infinitely with no response at all. I have to Ctrl-C to exit, whereupon it
> prints out
>
> svn: Network connection closed unexpectedly
> svn: Connection closed unexpectedly
>
> If I execute the following command (which is what I believe svn is trying to
> do)...
>
> D:\temp>plink.exe -l svn 192.168.1.1 svnserve -t
>
> ...then I get the expected response from the svnserve process.
>
> ( success ( 1 1 ( ANONYMOUS EXTERNAL ) ( ) ) )
>
> I also tried it with %SVN_SSH% set to "plink.exe -l svn". Same result
> (infinite wait).
>
> There is also an infinite wait if the client cannot find ssh.exe or the
> executable specified in the config file or %SVN_SSH%. No error message
> given. It must be given two Ctrl-C's to exit whereupon it prints nothing.
>
> What would be causing an infinite wait? Why would svn not report an error
> if it cannot find the defined ssh executable?
I'll let ghudson field this question...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 20 15:54:12 2003