httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Václav Krpec <>
Subject Re[3]: [users@httpd] Adding svn dbses without apache restart
Date Tue, 13 Jan 2004 09:08:06 GMT

JS> On Mon, 12 Jan 2004, Václav Krpec wrote:
>> JS> On Mon, 12 Jan 2004, [Windows-1250] Václav Krpec wrote:
>> >> I'd be glad if I must not restart
>> >> the server each time I add/remove a db (they are beeing
>> >> added by inserting a <Location> directive into httpd.conf).
>> JS> What's the problem with restarting the server?  If you use a graceful
>> JS> restart, there is essentially no effect on clients.
>> I know, but our company plan to offer hosting service with use of
>> svn database for each user; with hundreds (thousands?) of users =>
>> hundreds of <Location> directives in the config-file, how long will
>> the restart take?

JS> The graceful restart is instantaneous from the client's perspective.  Of
JS> course, it will increase load on the server since all the processes need
JS> to be recycled.  You wouldn't want to do it thousands of times per day.

Sure... I just wanted to know if I can do it in a nice way...

>> That's one thing, the another is that I really don't
>> think that it's impossible to map new dirs in run-time (AliasMatch
>> directive does it, don't it?).

JS> That is a question for SVN people.  [...Checks the SVN docs...]
JS> It looks to me like what you want is SVNParentPath:

JS> It's amazing what you can find by reading the docs ;-)

I've read the docs. SVNParentPath is fine, but don't work with
AuthzSVNAccessFile (for now), so every user is allowed to manipulate
every user's data... And that's the problem.

>> >> Why can't I place the <Location> directive into a .htaccess
>> >> file?
>> JS> Because <Location> works on URLs and .htaccess works on filesystem
>> JS> locations and there is not necessarily a direct mapping between them.
>> I see. But why it's impossible?

JS> Because there is no necessary mapping between URL and filesystem.  An
JS> .htaccess file in the foo/ directory does not necessarily have control
JS> over the foo/ URL space, so it would not be appropriate to allow a
JS> location directive controlling foo/.  (You don't want .htaccess files
JS> controlling parts of the URL space that they don't have rights to manage.)

JS> Joshua.

JS> ---------------------------------------------------------------------
JS> The official User-To-User support forum of the Apache HTTP Server Project.
JS> See <URL:> for more info.
JS> To unsubscribe, e-mail:
JS>    "   from the digest:
JS> For additional commands, e-mail:

  vencík <>

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message