Comments on: Keeping directories in sync with unison http://blog.melimato.com/keeping-directories-in-sync-with-unison/ Those things we do Sun, 22 Jan 2012 11:13:00 +0000 hourly 1 http://wordpress.org/?v= By: Rob Staveley (Tom) http://blog.melimato.com/keeping-directories-in-sync-with-unison/comment-page-1/#comment-229 Rob Staveley (Tom) Wed, 09 Sep 2009 13:20:33 +0000 http://blog.melimato.com/?p=104#comment-229 I also recommend considering having "CONFLICT" resolution in the profile. e.g. When both ends have been modified, prefer the local copy. [code] # Resolve conflicts in favor of local root prefer=/path/to/root/dir [/code] In particular this is good when you are sync-ing two directories which have already been duplicated. Unison makes a big song and dance of flagging all of the files as "CONFLICTS" in the log, which gets very large, if you don't start with a master at only one end. Alternatively, be sure to start with an empty directory at one end and then the conflicts will be genuine issues. A big thanks for this article pablo, it is a great way to get started! I also recommend considering having “CONFLICT” resolution in the profile.

e.g. When both ends have been modified, prefer the local copy.

[code]
# Resolve conflicts in favor of local root
prefer=/path/to/root/dir
[/code]

In particular this is good when you are sync-ing two directories which have already been duplicated. Unison makes a big song and dance of flagging all of the files as “CONFLICTS” in the log, which gets very large, if you don’t start with a master at only one end.

Alternatively, be sure to start with an empty directory at one end and then the conflicts will be genuine issues.

A big thanks for this article pablo, it is a great way to get started!

]]> By: Rob Staveley (Tom) http://blog.melimato.com/keeping-directories-in-sync-with-unison/comment-page-1/#comment-228 Rob Staveley (Tom) Wed, 09 Sep 2009 12:54:16 +0000 http://blog.melimato.com/?p=104#comment-228 I had this running nicely as it was from the command line, but saw /var/log/unison.log that it was bombing out when run from crontab with the following error: Sys_error("Broken pipe") My fix was to use nohup in the crontab: [code] */5 * * * * nohup /usr/local/bin/lockrun --lockfile=/tmp/hosting.lockrun -- /root/bin/my_unison_script.sh > /dev/null 2>&1 [/code] This seems to have done the trick. I had this running nicely as it was from the command line, but saw /var/log/unison.log that it was bombing out when run from crontab with the following error:

Sys_error(“Broken pipe”)

My fix was to use nohup in the crontab:

[code]
*/5 * * * * nohup /usr/local/bin/lockrun --lockfile=/tmp/hosting.lockrun -- /root/bin/my_unison_script.sh > /dev/null 2>&1
[/code]

This seems to have done the trick.

]]> By: SonyaSunny http://blog.melimato.com/keeping-directories-in-sync-with-unison/comment-page-1/#comment-2 SonyaSunny Sun, 10 May 2009 19:38:10 +0000 http://blog.melimato.com/?p=104#comment-2 Thanks for article. Everytime like to read you. Thanks for article. Everytime like to read you.

]]>