Are multiple 'Location' tags with same 'SVNParentPath' safe?

Good morning all,

I have a Subversion repository that is protected by mod_auth_ldap:

      <Location /svn>
        DAV svn
        SVNParentPath /usr/local/svn/repositories
        SVNListParentPath on
        SVNAutoVersioning on
        AuthName "Enterprise Shared SCM Repository"
        AuthType Basic
        Require valid-user
        AuthLDAPUrl ldap://primaryLdapHost...
        AuthLDAPBindDN ...
        AuthLDAPBindPassword ...
      </Location>

This works perfectly and we've been very happy with the results.

However...

I now have a different set of users who exist in a different LDAP
repository. They will ultimately (in 6-9 months) join everyone else but,
in the meantime, they need SVN access.

So, the question is, will it be safe to create (in the same httpd.conf) a
second <Location/> pointed to the same SVNParentPath?

      <Location /svnForOthers>
        DAV svn
        SVNParentPath /usr/local/svn/repositories
        SVNListParentPath on
        SVNAutoVersioning on
        AuthName "Enterprise Shared SCM Repository"
        AuthType Basic
        Require valid-user
        AuthLDAPUrl ldap://alternateLdapHost...
        AuthLDAPBindDN ...
        AuthLDAPBindPassword ...
      </Location>

If nobody has a definite answer, can anyone recommend test scenarios to
prove or disprove that this will or will not result in repository
corruption?

Related to this, and I will post it as a second query later, is it safe to
have multiple Apache instances pointed to the same SVNParentPath (e.g. --
clustering)?

Thanks,
James

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-17 14:58:41 CEST