--- Ed Hillmann <firstname.lastname@example.org> wrote:
> On 2/26/07, tien vuong <email@example.com>
> > Hello list members,
> > I am using TortoiseSVN-18.104.22.16801-RC1, and
> > svnserve-1.2.3 to serve remote clients.
> > Since
> > "svnserve only understands "blanket" access
> control. A
> > user either has universal read/write access,
> > read access, or no access. There is no detailed
> > control over access to specific paths within the
> > repository."
> > (http://svnbook.red-bean.com/en/1.1/ch06s03.html)
> > I used to run 2 instances of svnserver (each
> > at a different port) to allow remote accessing to
> > different repositories with different user access
> > permissions on each.
> > There has been inconvenience to run a svnserve
> > listening at a port different from the default
> > But I didn't know a better way.
> > Recently, I did an almost insane trial.
> > the trial showed that one svnserve can serve more
> > one repository with different user accounts for
> > /repos
> > /conf
> > /dav
> > /db
> > /hooks
> > /locks
> > /repos_1
> > /conf
> > ...
> > /repos_2
> > /conf
> > ...
> > First, I create an repository at /repos, leave its
> > configuration as default. Under /repos, I create 2
> > folders /repos_1 and /repos_2. I create 2 new
> > repositories at /repos_1 and /repos_2 and these 2
> > places are where my 2 different sources are really
> > imported. repos_1 and repos_2 have different user
> > lists configured in their passwd and svnserve.conf
> > files. svnserver root path is now pointed to
> > (svnserver -d -r C:\repos).
> > Surprisingly, from a remote PC, I can access
> > svn:\\[serverhost]\repos_1
> > and
> > svn:\\[serverhost]\repos_2
> > with different accounts registered for each
> > repository.
> > Though it seems wrong to create a repository
> > another repository location, what I can see is it
> > not more a problem than having one un-used
> > (/repos).
> > Has somebody tried that? Is it wrong or is there
> > bad side-effect?
> > Tien
> I haven't done it this way, but I have multiple
> repositories being
> serviced by a single svnserve process. I have a
> (/ct/ctsvn/repositories) in which I create the
> different repositories
> that will be handled by the svnserve daemon. So,
> /ct/ctsvn/repositories/repos2, etc,
> each with their own subdirs (conf, db, etc).
> Then, start svnserve in daemon mode as you were,
> passing the directory
> in which it will find the various repositories
> (svnserve -d -r
> This has worked for me just fine, since we've
> started using
> Subversion. It looks a bit cleaner than what you
> suggested, as each
> repository maintains its own files (there would be
> no difference if
> you decided you wanted to use different svnserve
> processes later on..)
> Hope this helps,
Ed, your configuration works for me. And yes, it is a
So this is one svnserve deamon for multiple
repositories. I've heard that new release of svnserver
can also support one repository with per-directory
access control, but it has some bug
(read access at root path must be granted for all
Anyone knows if the bug is solved?
No need to miss a message. Get email on-the-go
with Yahoo! Mail for Mobile. Get started.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Feb 27 04:07:24 2007