bug report: SUMMARY different files are not rsynced, identical files rsynced

[Peter Chun]

jw schultz wrote:

>On Thu, Jul 24, 2003 at 09:52:44AM +1000, Peter Chun wrote:
>  
>
>>Hi,
>>I have only just subscribe to the list.  ( only to send this bug report )
>>
>>Running rsync  version 2.5.6  protocol version 26 ( on Solaris 8 sparc ) 
>>on both hosts.
>>
>>I have 1 file I wish to sync to a remote machine
>>the md5 checksum is
>>
>>host1: MD5 (030722.mj) = 020397fde83c2e20464b6642c018ce6e
>>host2: MD5 (030722.mj) = 35fcffc896c65c8ec861385b4edb81ac
>>    
>>
>
>What is ls -l on them?  If that is the same it won't do
>squat.
>
Yes they are exactly the same.
timestamp, filesize.

ok This is the problem then.
Thanks

>  
>
>>If I make a copy of the file on host1 to /tmp
>>    
>>
>
>did you use "cp -p" or did you allow the copy to have a
>different modtime?
>
Could of swore I did, but the evidence proves otherwise.
different mod time on the copied files..... 8(

>  
>
>I'll bet the copy had differing timestamps.
>
yes they do.

I read everything about the algorithm and how rsync works
missed the initial ls -l check part.


Thanks for your help
Peter

--