[cvsnt] Betr.: sync-protocol questions

[Jan Keirse]

While it has long been on my todo list I have not yet gotten around using 
the sync protocol. 
However I remember talking about this on the CVSNT list and I think I was 
informed the commit would automatically be passed on to the master server. 
If you've already configured this sync protocol it would be easy to test 
on a dummy file to verify the result.

Kind Regards,

JAN KEIRSE
ICT-DEPARTMENT
Software quality & Systems: Software Engineer
Tel.:    +32 56 43 42 45
Fax:    +32 56 43 44 46
E-mail: jan.keirse at tvh.com
Contactsheet: JAN KEIRSE TVH FORKLIFT PARTS nv-sa -  BRABANTSTRAAT 15 - 
B-8790 WAREGEM 
Take a break to visit our site and tell us how we can help you today: 
www.tvh.com Before printing I think about the environment. 

cvsnt-bounces at cvsnt.org schreef op 29/09/2008 12:18:44:

> Hi,
> 
> I've been trying to read up on the sync protocol, but I've got some 
> questions left:
> 
> http://www.cvsnt.org/pipermail/cvsnt/2008-May/030642.html describes how 
to 
> use rsync/unison
> to perform the synchronization, either using a cronjob or a postcommit 
> hook.
> 
> 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?
> 
> Does the commercial version contain a more failsafe synchronization 
> option? 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?
> 
> Thanks,
> Carsten
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

**** DISCLAIMER ****
<A HREF="http://www.tvh.be/newen/pages/emaildisclaimer.html">
http://www.tvh.be/newen/pages/emaildisclaimer.html </A>

"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."