Failed rsync -- two different files considered up to date

2004-03-29 Thread Greger Cronquist
Hi, I've used rsync successfully for several years, syncing between two Windows 2000 servers using daemon mode, but today I stumbled accross something peculiar. I'm using cygwin with rsync 2.6.0 at both ends (the latest available at this date) and I have a file that rsync considers up to date

Re: Failed rsync -- two different files considered up to date

2004-03-29 Thread Craig Barratt
Greger Cronquist writes: I've used rsync successfully for several years, syncing between two Windows 2000 servers using daemon mode, but today I stumbled accross something peculiar. I'm using cygwin with rsync 2.6.0 at both ends (the latest available at this date) and I have a file that

Re: Failed rsync -- two different files considered up to date

2004-03-29 Thread Tim Conway
I hadn't thought of that one... I was going to suggest -c (--checksum). Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] Greger Cronquist writes: I've used rsync successfully for several years, syncing between two Windows 2000

Re: Failed rsync -- two different files considered up to date

2004-03-29 Thread Wayne Davison
On Mon, Mar 29, 2004 at 06:09:28PM +0200, Greger Cronquist wrote: I've tried calling rsync with several different options, most notably -c for forcing checksum, but it fails to see a difference between the files. If -c failed to notice that the files are different, then either (1) the MD4

Re: Failed rsync -- two different files considered up to date

2004-03-29 Thread Greger Cronquist
Thank you all! After some further, rather ugly, investigation it turned out that the original files (we found three of them!) had been corrupted by Windows. A fact I'm going to but in my growing pile of arguments for switching to a real operating system, at least for our servers. With that out