Posted May 13, 2011 21:06 UTC (Fri) by JohnMorris (subscriber, #73531)
[Link]
I have the same problem with Unison, to the extent that I now keep the installation files for one particular old version around to use every time I get a new machine.
Unison works well for synchronizing between two machines, and that's how I use it, to sync work files between home and work desktops. With three or more computers, though, you have to be careful what order you synchronize between them, or else things get into a mess. This is a result of its batch oriented way of working - syncs are manually initiated - and the lack of a central master repository which everything else syncs to. To be fair to the Unison authors, they do suggest that to keep multiple computers synced up one of them should be designated as the master and all others should sync only to/from that one.
Dropbox - which I also use, to keep my personal files co-ordinated between four or five computers - on the other hand is much friendlier in this regard, as it records deltas immediately.
Unison!
Posted May 15, 2011 0:11 UTC (Sun) by Velmont (guest, #46433)
[Link]
It is easy to build something similar around this. Using inotify, or incron, you can wait for close-signal, and then run unison on just that path-tree automatically.
I do something like that, only a bit less advanced with my unison script. I really love Unison, and it blows the butt of Dropbox and has for my kind of use. :-)
I have many machines, all of them using unison-323, it's not hard to standardize on a version, although yes, this could be easier.