Unison windows command line

You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. Create a free website or blog at WordPress. Share this: Twitter Facebook. Like this: Like Loading Tagged with: plink , ssh , sync , unison , windows. Integrating Jinja2 with django ». Leave a Reply Cancel reply Enter your comment here See the section "Profile Examples" of the user manual for further advice.

Another cause for this error can be the path to unison executable not quoted properly for 2. Changing the line to:. This is probably not a Unison problem as such. The usual reason for timeout problems is that Unison is taking a long time to compute fingerprints for a large amount of data that it has never seen before e.

A rule of thumb is that if your Unison is taking an hour or more to do what you expect then you may need to re-think your strategy to avoid problems with timeouts.

The best way to deal with this is to run Unison on smaller chunks of data, the first time. Later, when its archive is built and it just needs to check file modification times, scanning for updates is much faster and you can do everything all together. See the documentation of the "-path" preference for instructions on how to do this.

Sometimes network problems interrupt Unison's operation during large transfers of data from one computer to another. When this happens, Unison will conservatively delete all the data that has already been transferred. To prevent this, it often helps to create an empty folder structure on the target before starting transferring the data -- that way, the transfer will be broken up into small chunks and an interruption of network service will cause only one of them to fail and be deleted when Unison is re-run.

Unison 2. Create an empty directory in place of the non-existing directory to work around this problem. The versions of unison running on the server and the client must match. Specifically, the first two components of the version number must match exactly: versions 2. If all you need is the textual user interface, compiling binaries for most distributions is straighforward. We're not sure why this happens. It seems to be related to using the "backup" preference rather than the "backups"-with-an-s preference.

Work-around: manually create the directory it wants, then run Unison again. This problem occurs when you try to synchronize via SSH to your own local host.

You can use Unison to synchronize files that are on the same host computer, but not using SSH. To diagnose this situation, try the following on your local host. For example, suppose that the local and remote hosts are:. If you are getting the Unison "archives are locked" error, you will probably find that the remote IP address found in step 4 is the same as the IP address of your local host, not the IP address of the remote host.

Did you copy your profile files from a Windows machine? The problem most likely is that there are Windows-style end of line characters in the profile definition files, line feed characters to be more specific. You should use a utility like dos2unix to remove them, then unison should run fine.

This is actually not a unison problem, the same problem randomly arises when copying large files using scp over the same VPN connection. Yet, this prevents from using unison successfully. To see this, just type ifconfig on both machines and look at the MTUs of the network interfaces that are used by unison. As a result of this mismatch, some parts of messages are randomly lost search "MTU mismatch" on the internet.

Solution: adjust both MTU to similar values. For instance: ifconfig eth0 mtu on the remote server ifconfig tun0 mtu on my local machine. On some directories the anti-virus software is still scanning them, holding them open when Unison tries to rename the tmp directory to its final name. Hence the rename fails. Maybe your particular antivirus can allow patterns like.

Start a cygwin terminal by typing mintty on the Windows command line. In the mintty terminal, make a key pair by typing. Create the directory. Exit the mintty terminal. Unison needs to be installed on the remote fileserver which one of the Computer Officers will have to do.

Contact support ch. If keys have been set up correctly this will not prompt for a password and will display the unison version on the fileserver. If you do not want to use the command line version everything should now be set up to use the GUI version below. By using the '-times' option, file modification times but not directory modification times are propagated. Start the GUI with the following command or with a shortcut you have made to the executable. The Profile Creation Wizard guides you through this.

You wish to perform synchronization 'Using SSH'. Finally, Add the times Preferences variable with a value True.