I can say I no longer have any idea what causes svn+ssh to work
sometimes and not work others. I had installed subversion 1.3.1
binaries from Metissian on a Mac OS X machine at work. I was not able
to connect through ssh with the notorious "svnserve: command no found
error" which I read about in the FAQ. However, I installed the same
binaries on another Mac OS X and had no problems at all connecting
over svn+ssh with no configuration needed.
Stranger still, I removed all references to /usr/local/bin/ from my
path on this second machine in the /etc/profile and /etc/bashrc and
my account .bash_profile. I verified that this was true because when
logged into the computer via ssh, I had to qualify all the svn
commands with their full path. However, even then, when the svn
commands were nowhere to be found in the path, I could still connect
to this machine with svn+ssh with no message about svnserve not
found. Frankly, at this point, I don't know how the command could
have been found at all.
NOTE: i'm not using the public key method to connect over ssh so
there's no chance it was determining the path from the "command"
specified in the public key.
Any clues folks?
Bradley
-------------------------------------------------------
Bradley Mitchell Wagner
Software Developer
Hannon Hill Corporation
main: (678) 904-6900 ext. 115
email: bradley.wagner@hannonhill.com
-------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 8 08:36:45 2006