Re: svn+ssh

> Is it hanging or getting the connection closed message or something
> else? Connection closed usually meant the server side tunnel couldn't
> be started after ssh had connected, IIRC. This is using the command
> line client?

Here is the text from my original message:

I'm using plink.exe from PuTTY release 0.53b. I am using the official
distributions of Subversion 0.25.0 on Win32 and Linux.

The %APPDATA%\Subversion\config file contains the following lines

[tunnels]
ssh = plink.exe -l svn

'svn' is the account on the Linux box that owns the repository. plink.exe
is in %PATH% (it's in the same directory as svn.exe). I try to checkout a
working copy of the test repository with the following command.

D:\temp>svn co svn+ssh://192.168.1.1/usr/local/repos/test

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?

Sly

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 28 05:11:47 2003