Thank you Wayne for pointing me to these patches. I've never noticed
them before.
Am 24.05.2009 um 23:53 schrieb Wayne Davison:
On Sun, May 24, 2009 at 06:32:40PM +0200, Christian Hecht wrote:
Such a tool i plan to write for Mac OS X. The first time it should
store checksums and mod
Am 24.05.2009 um 18:01 schrieb Daniel Carrera:
Jamie Lokier wrote:
Daniel Carrera wrote:
But there is no way to distinguish between file corruption and a
legitimate change. All you can do is keep old backups for a few
days or weeks and hope that you detect the file corruption before
the b
w place.
Best regards,
Vitorio
Le 24 mai 09 à 15:05, Christian Hecht a écrit :
This will safe you if your file is corrupted on the backup side.
Rsync will copy it then again from the source because the checksum
is different and everything is okay.
But imagine the file is corrupted on the so
This will safe you if your file is corrupted on the backup side. Rsync
will copy it then again from the source because the checksum is
different and everything is okay.
But imagine the file is corrupted on the source side. Then rsync will
copy the corrupted file again and if you delete olde
Hello,
i am trying to implement a new feature for my rsync GUI RecPointX
under Mac OS X.
I want to store MD5 hashes for each source file. Later on i want to
proof if the source files are damaged.
So, for source files which are unchanged since last run, i want to
create the hash again a
Hello,
i am using rsync with Mac OS X 10.5.
Now i have downloaded the sources and patches for 3.0.4. and
sucessfully applied the fileflags.diff and crtimes.diff patches.
After reading in this mailing list i found there is also a patch to
preserve the last access time: atimes.diff
I wante
