> I think you're missing some fundamental concepts about how svn
> +ssh:// works. You should read this section of the book:
>
> http://svnbook.red-bean.com/nightly/en/
> svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshauth
>
> "The important thing to understand here is that the Subversion
> client is not connecting to a running svnserve daemon. This method
> of access doesn't require a daemon, nor does it notice one if
> present. It relies wholly on the ability of ssh to spawn a
> temporary svnserve process, which then terminates when the network
> connection is closed."
>
> The svn client is running 'ssh remotehost svnserve -t'. You don't
> need to do a thing on the server, other than have 'sshd' running
> and 'svnserve' installed.
>
To update, I read this stuff and here is where I stand. When I login
to my Mac from a linux machine via subversion from the command line
(svn list svn+ssh://host/path/to/repos), I got the following error
message:
svnserve: command not found
svn: Connection closed unexpectedly
I verified that svnserve was in the path of the user I was using to
login via ssh by ssh-ing into my Mac with that account and doing a
"which svnserve". Svnserve is installed by default in /usr/local/bin.
I got it to work by creating a symbolic link to svnserve in /usr/bin,
although I can't say I understand why that was necessary.
So, it's working from the command line now, but when I try the same
url in Subclipse, I got the following error:
Error validating location:
"org.tigris.subversion.javahl.ClientException: The system cannot find
the file specified. svn: Can't create tunnel: The system cannot find
the file specified."
Thoughts?
Bradley
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 24 17:39:49 2005