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

Re: [PATCH] svnserve to use a global configuration file

From: Blair Zajac <blair_at_orcaware.com>
Date: 2007-03-27 17:43:49 CEST

On Mar 27, 2007, at 2:09 AM, Erik Huelsmann wrote:

> On 3/27/07, Blair Zajac <blair@orcaware.com> wrote:
>> The point of the patch was not to have to read any per-repository
>> configuration files. It's not "overriding" the per-repository files
>> since they are never even read.
>> The bigger scope of this work was to have a Java Tomcat servlet be
>> able
>> to create thousands of repositories using JavaHL and not have to
>> populate all of them with the configuration files. I would rather
>> have
>> the servlet own the configuration files and spawn a svnserve
>> process and
>> hand to it with the --config-file option the svnserve configuration
>> files deployed with the servlet.
>> This skips the whole mess of having to create symlinks, which Java's
>> jave.io.File class does not support, so I'd have to shell out or
>> use a
>> native extension to Java to support.
>> As a side effect, this has a performance improvements.
> Would it be possible to delete the default files generated? Then, if
> they don't exist, an error reading them can be ignored when the
> --config-ifle option has been specified. That way, it's very clear the
> data from the local configuration isn't used (since there isn't any).

Yes, good idea. And currently, the code doesn't even attempt to be
open() the config files with the --config-file option.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 27 17:44:11 2007

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.