svnadmin won't fail if svnserve isn't running. After all, how can you run
svnserve without first creating the repository with the svnadmin command?
The "svnserve" command is the built in svn server for a single repository.
Most sites actually use the Apache httpd server to do this. Apache has built
in security and allows you to have multiple Subversion repositories. It also
automatically starts up on boot.
The "svnserve" command's big advantage is that it is simple. You run
"svnadmin -d -r $REPOSITORY_ROOT" and you're done. Quick and simple, and you
don't have to muck with Apache's configuration to get it to work. Something
to consider when you don't have administrative access to the machine, and
your System Admins aren't very helpful.
The problem with svnserve is that it can only handle a single repository on
a single port. The link I gave you before explains how to setup svnserve as
a Windows service. Remember to update the conf directory of the repository
you created. You need to update the conf/svnserve.conf file (basically, you
need the password-db parameter set to point to your passwd file. Simply
remove the "#" in front of that line), the conf/passwd file to specify who
can and cannot use the repository, and maybe the conf/authz file for finer
The files are pretty self explanitory. Good luck.
On Fri, Jun 12, 2009 at 3:04 PM, Bai Shen <baishen.lists_at_gmail.com> wrote:
> The CollabNet binaries install the server as a service.
> And wouldn't svnadmin fail if the server wasn't running?
> Hmm. I just looked and neither service was running. Odd. I started
> svnserve. However, when I tried to start the Apache service, it said it
> couldn't find mod_dav_svn.
> Now that I started svnserve, I'm getting a new error.
> c:\svn_repository\repos\conf\svnserve.conf:12: Option expected.
> Assuming that it means line 12, that line is the anon-access line in the
> defualt conf file. I commented it out and it skipped to the password line.
> So I think I'm missing something in the conf file, but not sure what.
> On Fri, Jun 12, 2009 at 2:47 PM, David Weintraub <qazwart_at_gmail.com>wrote:
>> Did you run the server? Subversion normally uses a Client/Server model, so
>> you need to run a server process that your Tortoise front end can talk to.
>> Did you run "svnserve"? Take a look at:
>> On Fri, Jun 12, 2009 at 2:38 PM, Bai Shen <baishen.lists_at_gmail.com>wrote:
>>> So I just installed a Subversion Windows server using the CollabNet
>>> binaries. I accepted all the defaults. Then I went into the svn-repository
>>> directory and ran "svnadmin create repos". BTW, this is in a Windows XP VM.
>>> Then I installed TortoiseSVN on my laptop(different from the machine
>>> running the VM). I tried using the repo-browser to connect to
>>> svn://ip/repos but it says the machine is refusing the connection. I also
>>> turned off the VM's firewall.
>>> Any suggestions for what I'm doing wrong? I'm trying to get the server
>>> setup and configure a new repository, but I can't figure out why it's not
>> David Weintraub
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-12 22:25:38 CEST