svn权限设置无效？

ld1978

svn权限设置无效？环境是windows+apache+subversion
svnserve.conf
### This file controls the configuration of the svnserve daemon, if you
### use it to allow access to this repository.  (If you only allow
### access through http: and/or file: URLs, then this file is
### irrelevant.)

### Visit http://subversion.apache.org/ for more information.

[general]
### The anon-access and auth-access options control access to the
### repository for unauthenticated (a.k.a. anonymous) users and
### authenticated users, respectively.
### Valid values are "write", "read", and "none".
### Setting the value to "none" prohibits both reading and writing;
### "read" allows read-only access, and "write" allows complete
### read/write access to the repository.
### The sample settings below are the defaults and specify that anonymous
### users have read-only access to the repository, while authenticated
### users have read and write access to the repository.
anon-access = none
auth-access = write
### The password-db option controls the location of the password
### database file.  Unless you specify a path starting with a /,
### the file's location is relative to the directory containing
### this configuration file.
### If SASL is enabled (see below), this file will NOT be used.
### Uncomment the line below to use the default password file.
#password-db = passwd
### The authz-db option controls the location of the authorization
### rules for path-based access control.  Unless you specify a path
### starting with a /, the file's location is relative to the the
### directory containing this file.  If you don't specify an
### authz-db, no path-based access control is done.
### Uncomment the line below to use the default authorization file.
authz-db = authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, they should
### have the same password database, and vice versa.  The default realm
### is repository's uuid.
realm = tjemp-svn Repository
### The force-username-case option causes svnserve to case-normalize
### usernames before comparing them against the authorization rules in the
### authz-db file configured above.  Valid values are "upper" (to upper-
### case the usernames), "lower" (to lowercase the usernames), and
### "none" (to compare usernames as-is without case conversion, which
### is the default behavior).
# force-username-case = none

[sasl]
### This option specifies whether you want to use the Cyrus SASL
### library for authentication. Default is false.
### This section will be ignored if svnserve is not built with Cyrus
### SASL support; to check, run 'svnserve --version' and look for a line
### reading 'Cyrus SASL authentication is available.'
# use-sasl = true
### These options specify the desired strength of the security layer
### that you want SASL to provide. 0 means no encryption, 1 means
### integrity-checking only, values larger than 1 are correlated
### to the effective key length for encryption (e.g. 128 means 128-bit
### encryption). The values below are the defaults.
# min-encryption = 0
# max-encryption = 256

[groups]
admin = admin
boss = yank
caiwu_m = wangping
caiwu_c = jialihong
jishuguihua_m = zhaobotao
chanpinyanfa_m = wangzhou
huiyuan_m = lvmiao
yfghz = zhuyunpeng,wangxuechao,menglingtao,hanfuyu,yanghui
yfghz_m = zhaobotao,wangzhou
hyktz = mengqinghui,qiyucen,gaolimin,panhao
hykt_m = lvmiao,xuruoyu
zhfwz = zhaofang,liudong,yangxiaozhu
zhfw_m = wanghao

authz文件配置
[/]
@admin = rw
@boss = rw
* = r

[/公司管理层]
* =

[/财务部]
* =

[/产品研发部]
* =

[/合规稽核部]
* =

[/技术规划部]
* =

[/交易部]
* =

[/风控部]
* =

[/结算部]
* =

[/人力资源部]
* =

[/市场部]
* =

[/会员部]
* =

[/综合部]
* =

[/分组SVN]
* = r

[/分组SVN/研发规划组]
@yfghz = rw
@yfghz_m = rw
wangping = rw
* = r

[/分组SVN/会员开拓组]
@hyktz = rw
@hykt_m = rw
wangping = rw
liudong =

[/分组SVN/综合服务组]
@zhfwz = rw
@zhfw_m = rw
wangping = rw
* = r

ld1978

搞定了，是apache的原因。。。