On Saturday 02 May 2009 23:33:38 Simon wrote: > hi there! > I've been using unison to synchronise and backup my computers. unison is > based on rsync IIRC but with the difference that it 'remembers' the state > of the folder that was synchronised. This way, if I delete a file on A, > when sync'ing it will be deleted on B. While rsync would leave the file on > B...
I assume you are syncing from A to B? In that case you should look at the various --delete* options to rsync > I see rsync as a very good 'cp' program, but I need something that can > deal with conflicts (file changed on both hosts/directories) and can > propagate changes like deletes properly. Is there a way to get this > behavior with rsync (maybe i missed something)? This cannot be done with rsync. It's very much an efficient scp replacement that works with deltas. And there is a definite source and destination, what you are describing is like how source repos work > The reason i'm asking is that unison has been having problems recently in > sync'ing two pc... On my laptop, when i start the sync, it first checks it > for changes against the 'unison snapshot'. Changes done since last sync > are those that will be propagated. But it takes so long to check for > changes (disk input rate is too slow i think) that once it finished, when > it's time to send the changes to the remote server, the remote end has > already disconnected! Surely unison has a --timeout or similar option? rsync has it, and it's such an obviously needed config option -- alan dot mckinnon at gmail dot com
