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

commit-access-control vs. AuthzSVNAccessFile

From: Lukas Ruf <ruf_at_rawip.org>
Date: 2004-04-19 14:32:51 CEST

Dear all,

fiddling around with subversion, appreciating subversion more
everyday, I stumbled over AuthzSVNAccessFile in the subversion book.

It has risen the following questions in mind:

- AuthzSVNAccessFile sections:
  Am I right that the sections support perl-regex as well?

    * =

    * = r

    * = rw

  would deny access completely to the projects a to e, allow read
  access to all projects f to i, and read-write access to the projects
  j to z.

- Is there any fundamental difference from a user perspective between
  AuthzSVNAccessFile and commit-access-control except that
  AuthzSVNAccessFile is more powerful by that it allows also to deny
  access to a project completely?

- Am I right that I do not need to restart apache2 every time I
  modified anything in an access control file of AuthzSVNAccessFile?

- Parent directories must be accessible if a directory must be
    * = r

    * = rw

    would work


    * =

    * = rw


Thanks for any clarification!


Lukas Ruf           | Wanna know anything about raw |
<http://www.lpr.ch> | IP? -> <http://www.rawip.org> |
eMail Style Guide: <http://www.rawip.org/style.html>|
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 19 14:33:29 2004

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.