sbrattla

Hi, Let's say I've got three storage nodes A,B and C. The process 'updateLog' which runs on each of the nodes regularly updates the content of a STATUS.LOG file. Let's say I set up BitTorrent to synch this file between A,B,C. Assuming that time is synchronized between the nodes, one should expect that all nodes at any given time contains the most recent file (timestamp-wise). 1) What happens if A updates STATUS.LOG, but can't get in touch with B and C? Will A simply attempt to retry synchronization until it gets in touch with B and C again? 2) What happens if A updates STATUS.LOG at the same time as B updates the STATUS.LOG - but A can't get in touch with B or C? Will A, when it again can establish contact with B and C, simply realise that it holds a stale version of STATUS.LOG and instead apply the version which B holds? Thanks!

@RomanZ Ad. 1 : does this mean that it is not capable of applying ownership + permissions as it was on the originating system?

Hi, I'm currently using csync2 + lsyncd to keep a few webservers synchronized. The way this works is that lsyncd keeps track of events on the filesystem, and invokes csync2 (rsync variant) to cascade changes to other servers. Even though this works fairly well, I'm curious as to whether BitTorrent Sync would be a better fit. However, I've got a couple of questions which I can't figure out for BT Sync: (1) When synchronizing directories and files between systems, how does BT Sync handle ownership and permissions? (2) If a file is changed on node A and also on node B, how does BT Sync handle conflicts? (3) Have I understood it correctly when I say that BT Sync operates more in a "star"-like fashion than in a "circle"-like fashion, meaning that system A may sync to system B and C, and B subsequently updates D and C updates E and F? Looking forward to anyone's insight on this.