Wow, thanks for that suggestion. You are exactly right. On one my
machine /usr/local/bin is in ssh's PATH and on the other it is not.
Hence the disparity. Is there a way to manually configure this PATH?
As far as I know I just did two vanilla installs of Mac OS X Tiger.
However, the PATH on the machine that does accept svn+ssh connections
includes some portions it looked like I must have manually added
somehow. Does ssh read from somwhere to determine its path?
Thanks for your help,
Bradley
-------------------------------------------------------
Bradley Mitchell Wagner
Software Developer
email: bradley.wagner@hannonhill.com
-------------------------------------------------------
On Apr 8, 2006, at 6:25 AM, Duncan Murdoch wrote:
> On 4/8/2006 2:35 AM, Bradley Wagner wrote:
> > 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?
>
> Sounds like a difference in the sshd configuration, assuming you're
> doing both connection attempts from the same client (so it's not a
> client config problem). What I'd suggest is that you do some
> simple diagnostic tests. For example, try
>
> ssh server printenv PATH
>
> to tell you the path that svn will see when it connects, and
>
> ssh server which svnserve
>
> to tell you where the svnserve command is located on the server
> (assuming it's findable). In these cases "server" should be the
> path to the server that you're testing.
>
> Duncan Murdoch
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 8 18:37:03 2006