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

Manage Security without Restarting Apache?

From: <steve.craft_at_sungard.com>
Date: 2007-09-10 16:02:46 CEST

Using SVN through Apache with client-side certificates. Settings in
ssl.conf (which reads client cert attributes like O or OU or etc) say who
can get into what repository. The svnaccess text file always has "* = rw"
for every repository so access is really just controlled through ssl.conf.

After adding a new repository with svnadmin at the command line, the
svnaccess file must have the new repository added, and then Apache needs to
be restarted.

After making a change to ssl.conf to modify read/write permissions, Apache
needs to be restarted.

Can anyone recommend a way to (better) handle access/entitlement through
Apache without having to restart Apache? One of the side effects of our
successful SVN implentation is that multiple new groups "want in", so the
distributed user count and repository count are growing horizontally and
vertically, so restarting Apache is becoming problematic.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 10 16:00:00 2007

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

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