In testing a long time ago I noticed that rsync under
Windows would appear to succeed when copying files that
had byte ranges locked by other programs (for example
Outlook's *.pst file) but the copy would have nulls
filling the locked portion. Does anyone know if this
is still the case with rsync 5.6, and is this a reasonable
way for a backup program to work? That is, should we
consider it better to get all we can from a locked file
or to report the error? Also, if this is still true it
probably means that we need the -c (always checksum)
argument to rsync since copies may appear to be complete
with matching sizes and timestamps when they aren't
exactly correct.
---
Les Mikesell
les < at > futuresource.com
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
