'''Unison''' is a bidirectional file synchronization tool that runs on Unix-like operating systems (including Linux, Mac OS X, and Solaris) and Windows. It allows two replicas of a collection of files and directories to be stored on different hosts (or different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other. It also unrestricted in terms of which system can be the host.

−

'''Unison''' is a file-synchronization tool for Unix and Windows. It allows two replicas of a collection of files and directories to be stored on different hosts (or different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other.

+

−

Not only can Unison sync between Windows and Unix ( OSX, Solaris, Linux etc.) systems, it also unrestricted in terms of which system can be the host.

+

== Installation ==

−

Common uses include syncing configuration files, photos, and other content.

In order to use Unison you need to create an profile, you can use a GUI or you can manually create a profile in {{Filename|~/.unison}}.

+

−

If you want to use the GUI, run:

+

=== GUI ===

+

+

To configure Unison with the GUI run:

$ unison-gtk2

$ unison-gtk2

−

Else, edit the default config file:

−

# nano ~/.unison/default.prf

−

First define the root of what you want to sync:

+

=== Manual ===

+

+

Alternatively, manually create a profile in {{ic|~/.unison}} and add the following lines to the default configuration file, {{ic|~/.unison/''profilename''.prf}}.

+

+

Define the root directory to be synchronized.

root=/home/user/

root=/home/user/

−

Then define the root where sync it too:

+

Define the remote directory where the files should be sychronized to.

−

root=ssh://example.com//path/to/server/storage

+

root=ssh://example.com//path/to/server/storags

−

Optionaly, you can give arguments to ssh:

+

+

Optionally, provide arguments to [[SSH]].

sshargs=-p 4000

sshargs=-p 4000

−

Now you are going to define which directories and files to include in the sync

+

Define which directories and files should be synchronized:

# dirs

# dirs

path=Documents

path=Documents

Line 36:

Line 37:

path=.bashrc

path=.bashrc

path=.vimrc

path=.vimrc

−

+

You can also define which files to ignore:

You can also define which files to ignore:

ignore=Name temp.*

ignore=Name temp.*

Line 42:

Line 43:

ignore=Name *.tmp

ignore=Name *.tmp

−

For further references check the Unison [http://www.cis.upenn.edu/~bcpierce/unison/download/releases/stable/unison-manual.html#profileegs documentation].

+

{{note|For more information see the [http://www.cis.upenn.edu/~bcpierce/unison/download/releases/stable/unison-manual.html#profileegs Sample profiles] in the [http://www.cis.upenn.edu/~bcpierce/unison/download/releases/stable/unison-manual.html User Manual and Reference Guide].}}

+

+

== Usage ==

+

+

Once your profile is set up, you can start syncing:

+

$ unison ''profilename''

+

or using the GUI tool:

+

$ unison-gtk2

+

and select the profile. Unison has a nice interface where you can view the progress and changes.

+

+

== Version incompatibility ==

+

+

For Unison to function properly, the same version ''must'' be installed on all clients. If, for example, one computer has version 2.40 and the other has 2.32, they will not be able to sync with each other. This applies to ''all'' computers that share a directory to be synchronized across your machines.

+

+

Due to the staggered releases with varying Linux distros, you might be stuck with older versions of Unison, while Arch Linux has the latest upstream version in the Extra repository. There are unofficial [[PKGBUILD]]s for versions 2.32 ({{AUR|unison-232}}) and 2.27 ({{AUR|unison-227}}) on the [[AUR]] that allow users of multiple distros to continue using Unison with their existing systems.

+

+

== Tips and tricks ==

+

+

=== Save human time and keystrokes ===

+

+

If one runs unison within a VDT emulator capable of maintaining a suitable scrollback buffer, there is no purpose in having to confirm every non-conflicting change; set the {{ic|auto}} option to true to avoid these prompts.

+

+

=== Common config sync ===

+

+

When syncing configuration files which would vary (e.g., due to endemic applications, security-sensitive configuration) among systems (servers, workstations, laptops, smartphones, etc.) but nevertheless contain common constructs (e.g., key bindings, basic shell aliases), it would be apt to separate such content into separate config files (e.g., {{ic|.bashrc_common}}), and sync only these.

+

+

{{Warning|Bidirectional syncing of config files can lend itself to become an avenue for an attack, by enabling the peer syncing system to receive malicious changes to config files (and perhaps even other peers the system syncs with). This is an attractive option for adversaries, especially when the conceptual security levels of the two systems differ (e.g., public shell server vs. personal workstation), since it would likely be simpler to compromise a system of lower security. Always use the {{ic|noupdate}} option when bidirectional syncing between two particular systems is deemed unnecessary; when necessary, verify each change when syncing. Automatic bidirectional syncs should be done with extreme caution.}}

−

==Usage==

+

== See also ==

−

When your profile is setup you can start syncing:

+

−

$ unison <profilename>

+

−

Or:

+

−

unison-gtk2

+

−

And select the profile. Unison has a nice interface where you can view the progress and changes.

Revision as of 12:37, 29 October 2013

Unison is a bidirectional file synchronization tool that runs on Unix-like operating systems (including Linux, Mac OS X, and Solaris) and Windows. It allows two replicas of a collection of files and directories to be stored on different hosts (or different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other. It also unrestricted in terms of which system can be the host.

Usage

and select the profile. Unison has a nice interface where you can view the progress and changes.

Version incompatibility

For Unison to function properly, the same version must be installed on all clients. If, for example, one computer has version 2.40 and the other has 2.32, they will not be able to sync with each other. This applies to all computers that share a directory to be synchronized across your machines.

Due to the staggered releases with varying Linux distros, you might be stuck with older versions of Unison, while Arch Linux has the latest upstream version in the Extra repository. There are unofficial PKGBUILDs for versions 2.32 (unison-232AUR) and 2.27 (unison-227AUR) on the AUR that allow users of multiple distros to continue using Unison with their existing systems.

Tips and tricks

Save human time and keystrokes

If one runs unison within a VDT emulator capable of maintaining a suitable scrollback buffer, there is no purpose in having to confirm every non-conflicting change; set the auto option to true to avoid these prompts.

Common config sync

When syncing configuration files which would vary (e.g., due to endemic applications, security-sensitive configuration) among systems (servers, workstations, laptops, smartphones, etc.) but nevertheless contain common constructs (e.g., key bindings, basic shell aliases), it would be apt to separate such content into separate config files (e.g., .bashrc_common), and sync only these.

Warning: Bidirectional syncing of config files can lend itself to become an avenue for an attack, by enabling the peer syncing system to receive malicious changes to config files (and perhaps even other peers the system syncs with). This is an attractive option for adversaries, especially when the conceptual security levels of the two systems differ (e.g., public shell server vs. personal workstation), since it would likely be simpler to compromise a system of lower security. Always use the noupdate option when bidirectional syncing between two particular systems is deemed unnecessary; when necessary, verify each change when syncing. Automatic bidirectional syncs should be done with extreme caution.