Here is what i will do.
I have two servers. on one server i will create master source code
repository say mast_repo and now this repository i want to replicate
to another server.
here is what i have done
i have created two repositories and fired the following command.
[root_at_svntest svn]# svnsync init
svnsync: DAV request failed; it's possible that the repository's
pre-revprop-change hook either failed or is non-existent
svnsync: At least one property change failed; repository is unchanged
svnsync: Error setting property 'sync-lock':
could not remove a property
is there anything missing??
On Mon, May 4, 2009 at 9:11 PM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
> Lira Olavo wrote:
>> I have a question over this problem, if I don’t want to have the slave read-only, is there an easy way of doing it?
>> I was wondering in implementing some triggers that would warn the other servers when someone is doing a commit so no one could do a commit at 2 places at the same time… is there another way of doing it? Really having multi site repositories where everyone reads and writes in all projects?
> That's basically what happens - you write to one and then the svnsync writes to the others. You just need to agree on a master where you proxy all of the direct writes to avoid race conditions - and the clients don't need to know anything about it. Being able to read from the local copy is a plus for efficiency.
> Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-05 15:08:36 CEST