[cvsnt] sync-protocol questions
arthur.barrett at march-hare.com
Mon Sep 29 13:01:50 BST 2008
> I'm wondering what would happen if a client commits something
> to a slave,
> which is currently
> not in sync with the master (with just one server they would have a
> conflict). The slave would
> probably happily accept the commit, but the next rsync would
> fail due to
> the conflict, I suppose?
No - it is as Jan already replied. The slave passes all the writes to
the master which would then fail the commit. The system is failsafe in
> Does the commercial version contain a more failsafe synchronization
If you want assurance then commercial support is definitely the way to
go. We currently only commercially support the synchronised
repositories with several days of on site work at each location in
addition to the Pro Level 4 or 5 support contract to ensure everything
is set up and tested - but we expect that's what most organisations that
are large enough to need sync support want. Either late this year or
early next year we'll have a more 'out of the box' solution where the
customer is more responsible for the installation.
> Also, does it work
> synchronously or asynchronously on commit, i.e. would a
> commit have to
> wait until the synchronization
> to all slaves is finished?
We have ours set up as asynchronous, but it's entirely up to you how you
script your triggers. If your server is on windows then setting up
asynchronous is a bit difficult - the commercial version does include a
sync trigger partially for this purpose.
More information about the cvsnt