On 26/07/10 23:15, Jim Lord wrote: > I’m setting up a write-through proxy mirror. I can run: > [snip] > > BUT, I can’t run: > > svnsync init --source-username svnsystem --source-password $pass > --sync-username svnsystem --sync-password $pass > https://versiontest1.divxnetworks.com/svn/vtest file:///data/svn ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[snip] > I do have these on the slave’s httpd configuration files: > [snip] > <Location /svn/vtest> > > DAV svn > > SVNPath /data/svn/vtest > > SVNMasterURI https://versiontest2.divxnetworks.com/svn/vtest > > … > > </Location> You can't svnsync to something that's configured with SVNMasterURI and therefore trying to proxy the write requests to the master, can you!? > <Location /svn-proxy-sync> > > DAV svn > > SVNPath /data/svn/vtest > > Order deny,allow > > Deny from all > > # Only let the server's IP address access this Location: > > Allow from 172.16.4.134 > > </Location> So shouldn't the svnsync be: svnsync init --source-username svnsystem --source-password $pass \ --sync-username svnsystem --sync-password $pass \ https://versiontest1.divxnetworks.com/svn-proxy-sync \ file:///data/svn On another note (if practical) I can tell you that svnsync via the svn:// protocol is _much_ quicker than via http(s). John. -- John Beranek To generalise is to be an idiot. http://redux.org.uk/ -- William Blake
