On Mar 1, 2006, at 09:25, Stefan Schwarzer wrote:
> c) So, from this test server I try to connect to my local machine
> as follows:
>
> /usr/bin/svn checkout svn+ssh://schwarzer@my.ip.address/Users/
> schwarzer/Documents/subversion_cvs/geodataportal/trunk .
> Password:
>
> d) But then I get the following error message:
>
> bash: line 1: svnserve: command not found
> svn: Connection closed unexpectedly
>
> e) I started the svnserve on my local machine (and on the test
> server too, cause I wasn't sure which svnserve it is asking for) using
>
> svnserve -d
>
> f) I tried to connect via SSH from the test server to my local
> machine and start svnserve and it works as well.
Using svn+ssh, you do not need to start svnserve yourself, and if you
do start it beforehand, that instance never gets used. Rather,
svnserve gets started automatically whenever anyone connects. But the
way it gets started is that svnserve needs to be in the path of the
user who's connecting. There are several files that bash can read in
and in which such a path could be defined, and I believe the
configuration file used when you connect over svn+ssh is different
from the one used when you connect normally over an ssh terminal,
which might explain why you can start it when you log in via ssh but
not when Subversion tries to connect. Search the mailing list
archives; I'm sure this has come up before.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 1 12:34:53 2006