[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnserve config file

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-04-21 21:37:12 CEST

On Mon, 2003-04-21 at 14:25, Jeff Cave wrote:
> Where does the svnserve config file go so that it knows who to accept connections from?

I think you're confused. Or rather, I think the book is confusing. :-)

You have three options:

1. If you run svnserve as a daemon, then it listens on a certain port
and accepts all incoming connections from all hosts, without any
authentication. It accesses the repository as whatever user 'svnserve'
is running as. This is best for anonymous read-only access.

2. If you configure inetd to launch svnserve instead, then you can
probably configure inetd to reject certain host IPs; not sure about
that, though.

3. Finally, you can simply give your users SSH access to the server, and
they can configure their svn clients to launch a remote, private
svnserve process via SSH. (After doing SSH authentication, of course.)
No need to run a daemon here at all. The 'servers' file is referring to
the *client* run-time config file, typically in ~/.subversion/. Clients
edit this file to indicate how they want to launch a remote SSH process.

You're the second person to read the 'svnserve' section of the book and
ask this question -- somehow people think that the 'servers' config file
has something to do with setting up a server daemon. It doesn't. We're
talking about client setup here.

Cmpilato/fitz, I guess we should add this to our list of book to-do
items. That section needs to be made clearer.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 21 21:38:28 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.