file-copy corruption

[T. Horsnell]

>Il giorno gio, 29/06/2006 alle 14.41 +0100, T. Horsnell ha scritto:
>
>> OK, I'm convinced about using rsync to build the filesystem copy.
>> gnu-tar over NFS seems to take about 50% longer.
>> However, as far as I can tell, rsync uses the file-modification time
>> to determine whether a source and destination file are possibly different
>> (or the file length if --size-only is selected), and only if these
>> indicate that the files may be different does it start to look at the
>> differences. Yes/no?
>This is the predefined mode when rsync is used locally, for example for
>copying from one dir to another.
>
>But if you copy between servers, and you have a good configuration,
>rsync can check for differences even if date and size are the same

Yes, but what triggers it to start doing this? If the date and size
of the files on the local and remote machine *are* the same, how do
you force it to to do the crc check? What is a 'good configuration'?

Cheers,
Terry.


>
>It use crc check, and md4 to recognize which part of the file remain the
>same and are not to be transferred.
>
>Bye
> Ambrogio
>
>-- 
>fedora-list mailing list
>fedora-list at redhat.com
>To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>