Yeah Unisons conflict resolution isn't great, it simply doesn't replicate conflicting files when run as a script in batch mode, you can run it in user mode and it will warn on conflicts prompting you on which to keep. I would prefer it copy the file to another directory that gets replicated something like replicaroot/servername/path/to/file/filename, but my use for Unison is only for fail over access to these files so conflicts should be minimal. I get around all of this making it a bit more robust by running a cron that md5deep's the roots at each of the servers then verifying the md5s are right on all servers, then emails me failures.
-- Regards Morgan Storey On Thu, Jul 15, 2010 at 11:37 PM, Daniel Pittman <[email protected]>wrote: > Morgan Storey <[email protected]> writes: > > > What do you mean? it is a manual initial sync to get the files in sync > (just > > copy the different files either way and work out which ones you need to > > trash or merge) Then startup your unison scripts and let the servers > build > > there indexes then sync. > > Ah. Yes, that is fair, you can do that. What conflict resolution strategy > does it use in that mode? I presume some variant on "preserve the lot", > which > is what I would use. > > Um, and yeah: you are dead right it can do that effectively. > Daniel > > -- > ✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 > 707 > ♽ made with 100 percent post-consumer electrons > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
