The weird errors I was getting earlier this week with Rsync checksumming
files that really shouldn't be checksumed at all does not occur in 2.3.2.
We dug in to the code and put in a bunch of extra debugging messages to try
and track it down, but it seemed almost entirely random. You could run
rsync on one directory, say, /c/windows, the first time it would checksum
nearly every file, the second it wouldn't checksum any. We would then run
Rsync on /c/coreldraw and it would work the same. But then immediately
after, go back and do /c/windows, and it would re-checksum all the files
again.
It would also checksum /c/ every time rsync was run regardless. 2.3.2 also
seems quite a big faster, but I have no hard facts to back that up.
What features would I be missing if I were to use 2.3.2 instead of 2.4.3?
Thanks.
