This article needs additional citations for verification. (July 2021) |
Developer(s) | Benjamin Pierce and contributors |
---|---|
Initial release | 1998[1] |
Stable release | 2.53.6[2]
/ 4 November 2024; 5 November 2024 |
Repository | |
Written in | OCaml |
Operating system | Linux, macOS, Windows |
Type | Synchronization |
License | GPLv3 |
Website | github |
Unison is a file synchronization tool for Windows and various Unix-like systems (including macOS and Linux).[3] 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.[4][5][6][7] Syncing replicas directly Unison is independent of third-party providers.
Features of Unison include to handle file changes on both sides of replication; conflicts (same file changed on both sides) are displayed and can be resolved manually, optionally creating backups of changed files. Unison allows synchronization via computer networks (LAN, Internet) by direct connection (socket) or tunneled via ssh.[8] By using the rsync algorithm only changed blocks of files have to be transferred, thus saving bandwidth.
Unison can be called via the command line with parameters or controlled via profile files.[9][10] It can be executed interactively or batch-controlled automatically. In batch mode, unique changes are automatically synchronized. Files with replication conflicts are skipped.
After startup, Unison checks the file inventory per directory or computer and compares the timestamps of the files. If it detects changes, the changes to the corresponding files are analyzed in more detail. Afterwards Unison creates a replication list with suggestions for their synchronization and marks conflicts that cannot be resolved automatically.
GUI versions of Unison exist for interactive use. Under Windows and Linux they are generally based on GTK+. The GUI versions allow an easier overview of the replicas and the proposed synchronization. Changes can be marked individually by keyboard or mouse and then implemented in bundles.
Compared to rsync, Unison is fully bi-directional and allows the user to detect and reconcile conflicts when both copies of a file have been changed since the last synchronization.
Before version 2.52, a frequent hassle for users was that both computers needed to run the same version of Unison, compiled with the same version of the OCaml libraries.[11] This creates problems, since, e.g., Debian Linux's APT system will not provide the ability to install an arbitrarily chosen version of the software or one compiled with any desired version of the OCaml libraries, if that is what is required by a second machine running a different operating system or packaging system. This was solved in version 2.52: both client and server can run different versions of Unison, compiled with different OCaml versions, as long as both sides are running at least version 2.52. If one end is running version 2.48 or 2.51, the other end may run any version from 2.52 but the OCaml version must match.[12]
Unison differs from Syncthing in several ways, the main one being that Syncthing is designed for always-on, automated synchronization, whereas Unison is designed for synchronization that is triggered and monitored by the user. Syncthing is peer-to-peer, while Unison is not.
{{cite web}}
: Missing or empty |title=
(help)