--compare-dest; I'm missing the boat

Matt McCutchen matt at mattmccutchen.net
Sat Jan 17 22:33:15 GMT 2009

On Sat, 2009-01-17 at 14:57 -0600, Harry Putnam wrote:
> Matt McCutchen <matt at mattmccutchen.net> writes:
> > You know, there are two-way synchronization tools such as unison
> > ( http://www.cis.upenn.edu/~bcpierce/unison/ ) that are designed for
> > this situation and would make your job much easier.
> I was experimenting with unison when I hit on the scheme I laid out.
> I thought unison was pretty punky compared to rsync.
> Unless you use the gui version you never see the big picture.  The gui
> is pretty lame too, but mostly it isn't an option very often.

What's wrong with the GUI?  I used it for a few weeks when I was making
the transition from one machine to another and needed to keep certain
directories synchronized between the two; I thought it worked fine.

> What I
> need to see (on occassion) is some indicator that I need to overwrite
> completely one way or the other.

Unison will overwrite each file in the proper direction based on which
side changed since the last run.  I figure that every decision I make
has some chance of error, so having a program make the right decision
for me is a win.  What's not to like?

> Also what would queer things with unison is that active work happens
> in /cvsb with all the concomitant *~ files, partial unfinished
> scripts, temporary directories and files that can produce.

I don't see why this would be more of a problem with unison than with
rsync.  They both let you exclude files by name or path.


More information about the rsync mailing list