search for: radius13a

I've started testing the detect-renamed patch with 2.6.9 and soon 3.0.0pre1. I have an unique situation where I'm rsync'ing to a HSM based filesystem. I've found that the detect-renamed patch works but it appears to do a copy of the file to the new destination. This is particular slow since the file in the HSM based filesystem may only be a stub and all the data is only resident

Any concerns with the compiler warning on flist.c on a ia64 system running SLES10SP1? ~/rsync-3.0.0pre7> make gcc -std=gnu99 -g -O2 -DHAVE_CONFIG_H -Wall -W -o mkrounding -I. ./ mkrounding.c ./mkrounding >rounding.h Rounding file_extras in multiples of 2 (EXTRA_LEN=4, FILE_STRUCT_LEN=24) gcc -std=gnu99 -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c flist.c -o flist.o /tmp/ccqjJwNs.s:

Hi, I am learning rsync mechanism. My understanding is that rsync reads a file into multiple chunks and calculates every byte for MD5 and rolling checksum for each chunk.. On the other side of file system, it compares two checksums for each chunk in the same file to decide if two files are equal or not. Is it correct? If it is correct, should I worry the calculation time if I have thousands large