I use both rsync and unison. Unison works as adverrtised; it will sync both sides or die trying. It has some disadvantages: it knows nothing about users, permissions, or system times. The receiving system gets the file with the current date, and the user and permissions of teh user running unison, so it's not a perfect sync. The developers are working on that, but since unison is a true cross-platform sync, they are having one heck of a time apparently. I use rsync for the bulk of my transfers which are one-way, and the small part that is two-way is scanned to find the files transferred by unison and owner and perms set by a cron job. It does leave a window of aobut 6 hours at night between the sync and the cron job that the two systems are out of sync owner and permissionwise. --Yan > For an rsync-like tool, you might want to check out "unison" > <URL:http://www.cis.upenn.edu/~bcpierce/unison/>, in some sense it's > a companion project to rsync, and recently got the rsync > distributed-update algorithm added to it. > > Unison does some things that rsync doesn't. If you were to lock your > system clocks reliably in perfect sync, if no program ever dorked > with a file's timestamp, and if you never ever modified the same > file on both ends between syncs, then an "rsync -u" in each > direction would (I believe) do the same thing. But unison doesn't > require those guarantees, and it raises an alarm if a file is > modified on both ends. Or at least so the documentation claims, I've > not actually used it (I only download sources, and haven't gotten > excited enough about Unison to bootstrap myself an Objective CAML > development environment:-). > > -Bennett
