On 8/14/06, James Hagstrom <james.hagstrom@vistatsi.com> wrote:
>
> I'm just running TSVN on the client. Should I run this on the server?
> What are the benefits?
It only matters in that you have to have the server name or ip address
in the url. 'localhost' is a sort of shortcut name for 'this
machine'. So if you use 'localhost' as the server name it is going to
try to contact the machine you are running on, not the real server.
>
> I changed "localhost" to the IP address on the server and it says no
> repository found.
Good, that's progress...you've contacted the server now and got a
response back from svnserve.
>
> The command that I run on the server is just the .exe file w/ no
> parameters. I thought it had to have at least -d but it keeps running.
>
How did you install the actual Windows service (it does not get
installed through the normal install package so you must have used a
helper package of some kind)? It appears to not be pointed at your
repositories correctly. Usually, you pass the -r option with the
parent directory of where you repositories are located.
For example, 'C:\Subversion\svnserve.exe -d -r D:\Repositories' and
then you can have repositories under D:\Repositories (created with
'svnadmin.exe create D:\Repositories\Junk' or similar). Then you
would refer to that repository with a url like:
svn.exe ls svn://servername/Junk
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 15 03:25:42 2006