Am Donnerstag, 29. April 2004 09:28 schrieb Ulrich Eckhardt:
> Guy Umbright wrote:
> > I can successfully ssh to the client machine and do "svnserve -i", with
> > no problem, getting
> >
> > ( success ( 1 2 ( ANONYMOUS ) ( edit-pipeline ) ) )
> >
> > But strangely if I do:
> >
> > ssh <servermachine> svnserve -i
> >
> > I get the same messages as with the svn command. If I do the following
> > though:
> >
> > ssh <servermachine> /opt/local/bin/svnserve -i
> >
> > getting:
> >
> > ( success ( 1 2 ( ANONYMOUS ) ( edit-pipeline ) ) )
> >
> > /opt/local/bin is indeed in the the path for the account, so I don't
> > get what the hell is going wrong. I will accept
> > any ideas, as well as any dopeslaps. What did I mess up?
>
> Well, I'd guess the paths for that account. Beware, there might be wore
> than one place to set the path. I think, by default, ssh starts a /bin/sh
> when invoking another process and /bin/sh probably wont read ~/.bashrc,
> even if that is the user's shell.
If you're executing 'ssh <server> <command>', neither bash nor sh are started.
Instead, the <command> is started directly, and it is searched for <command>
in the directories indicated by the PATH evironment variable.
And according to the ENVIRONMENT section of the ssh manpage:
PATH Set to the default PATH, as specified when compiling ssh.
So you may put a symbolic link to your svnserve in /usr/bin (as I did), or
recompile ssh.
HTH,
Dirk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 29 15:25:11 2004