Matt McCutchen wrote:
> Second, it is impossible to make xattr-based checksum caching
> foolproof against same-second modification. Suppose a file is written
> during second 5 and then rsync caches its checksum during second 8;
> now the file has mtime 5 and ctime 8. Sometime later, rsync notices
On 6/30/07, Wayne Davison <[EMAIL PROTECTED]> committed:
Added Files:
checksum-xattr.diff
Log Message:
A simple patch that lets rsync use cached checksum values stored in
each file's extended attributes. A perl script is provided to create
and update the values.
Wayne,
You should be a
On 6/30/07, Wayne Davison <[EMAIL PROTECTED]> wrote:
On Sun, Jun 24, 2007 at 01:03:03PM -0400, Matt McCutchen wrote:
> Specifically, it has protection against being fooled when a file's
> checksum is cached and the file is modified again in the same second;
> .rsyncsums could use this.
I tried t
On Sun, Jun 24, 2007 at 01:03:03PM -0400, Matt McCutchen wrote:
> The git index has been heavily used and tested, so you might find it
> helpful when implementing a checksum cache for rsync.
The problem with this is that the git cache is SHA1, and rsync needs
both MD4 and MD5, depending on what pr
On 6/30/07, Adrian Marsh <[EMAIL PROTECTED]> wrote:
I'm trying to rsync up to some centos repositories, but I only want to
pull down the i386 and i386_64 folders with their RPMs, I've tried
various combinations and include and exclude, and I'm sure that the
below should work, but it doesn't...
S
Hi,
I'm trying to rsync up to some centos repositories, but I only want to
pull down the i386 and i386_64 folders with their RPMs, I've tried
various combinations and include and exclude, and I'm sure that the
below should work, but it doesn't...
SOURCE=rsync://mirror.stanford.edu/mirrors/centos
