I think I've heard that the file that's read when you log in
interactively via ssh (.profile) may not be the same file that gets
read when you log in non-interactively via ssh for example when it's
trying to start up svnserve. Unfortunately I don't recall the name of
the file that it might use instead.
On Apr 18, 2008, at 5:13 PM, Fred A Cantley wrote:
> First off, thanks for the very quick reply, especially on a Friday
> We are using an FSFS repository on Sun Solaris 10. The vendor's
> machine is also a Sun Solaris 10 box (supplied by us, so it is
> setup the
> I setup a '.profile' with the proper path and ld_library_paths
> just in case the sub shells were not inheritting the env properly.
> I also
> took the "--password" off the command (which was for authenticating
> in svn,
> but I turned off svn's authentication for now).
> However, I am still getting the same results. I also verified that
> the svn
> utilities were in the path with the which command and just did an 'svn
> help' and got a proper response for that (not needing a repository for
> Again, thanks for the suggestions, and I still appreciate any other
> thrown my way.
> Stefan Sperling wrote:
>> On Fri, Apr 18, 2008 at 03:50:10PM -0500, Fred A Cantley wrote:
>>> I am having problems getting a vendor's machine to access our
>>> with svnserve and svn+ssh. I can ssh to their machine and ssh
>>> back to
>>> ours, so I don't think it is not a problem with ssh.
>>> We are running svn version 1.4.4 on the repository and client
>>> I have tried setting up svnserve on the repository machine in the
>>> following ways:
>> You don't need to start an svnserve daemon for svn+ssh://
>>>> svn -d -r /path/to/repo
>>>> svn -t -r /path/to/repo
>>>> svn -t -r /path/to/repo --listen-port=22
>>>> svn -t -r /path/to/repo --listen-port=3691
>>> then try to access it from the client machine with:
>>>> svn list svn+ssh://our.host.ip/path/to/repo --password
>> Authentication is done internally by ssh.
>> --password isn't for use with svn+ssh://, it's for use with svn://,
>> http://, and https://
>>> then enter my Unix password at the prompt and get the response:
>>> ksh: svnserve: not found
>> Hey, this is OpenBSD, right? :)
>> Make sure the PATH is correct. I'm not sure if the default PATH
>> for ksh contains /usr/local/bin. Check the .profile of the user
>> you're logging in as.
>>> svn: Connection closed unexpectedly
>>> $ which svn
>>> $ which svnserve
>>> I have also tried starting up an svnserve from the client side,
>>> trying to
>>> point to the host machine and got the same response:
>>> svnserve -t -r ssh://our.host.ip/path/to/repo
>>> I would really appreciate any help I can get.
>> Hope I could help you.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-19 01:00:41 CEST