Hello,

On 18-09-2009, T o n g <mlist4sunt...@yahoo.com> wrote:
> On Fri, 18 Sep 2009 08:03:47 +0200, Emanoil Kotsev wrote:
>
>>> This is mainly use to synchronize files and directories between my
>>> notebook and desktop (at home and at work). Any good recommendation?
>>> . . .
>> Hi, so far I have not found any nice and useful software that can do
>> this (I mean with gui and so on)
>> 
>> The mentioned unison program failed the tests. May be rsync but not sure
>> it didn't do the things I wanted and I wanted to do it the way you can
>> do it in i.e. windows with some commercial software.
>> 
>> I was also thinking unison is just the right thing, but then I noticed
>> it's not really syncing like it should and leading to inconsistency.
>
> Thanks for your feedback, Emanoil. Could you elaborate more? unison 
> "looks" promising to me, and I've just learned that there are no ocaml 
> runtime dependency for it on i386, amd64. So usability is the most 
> important issue to me now. Anyone has positive experience with unison?
>

I am using it daily for synchronization of my /home between:
- home computer and server 
- home computer and work computer
- home computer and notebook

I also from time to time synchronize part of my /home tree to Windows
(i.e. the part containing my source code).

Works flawlessly (and automatically) since years. Never have problems,
except very long transfer when there was very big files... (but this is
due to standard bandwidth problems).

If there is any inconsistency I think it related to software that use
file synchronized. I.e. if you don't close iceweasel and synchronize its
files, you can get inconsistency because iceweasel can still handle data
not on your hard drive during synchronization. 

The other most obvious problem that can exists is also for the first
synchronization. In this case unison don't know yet what host to trust
for synchronization. E.g. if both computers hold a copy of file A, unison
don't know in which way it should be synchronized. It is the same if
there is a file A on one host and not on the other. Once this first
synchronization is done, unison remember the state of the last
synchronization point and use it: if you remove file A on one host it
will understand that it should remove it on the other host. 

Regards,
Sylvain Le Gall


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to