(fwd from firstname.lastname@example.org) thanks and patch
dwd at bell-labs.com
Fri Mar 22 01:39:44 EST 2002
On Wed, Mar 20, 2002 at 03:19:37PM -0800, jeremy bornstein wrote:
> On Thu, Mar 21, 2002 at 10:07:14AM +1100, Martin Pool wrote:
> > It sounds like you're using asymmetric encryption. So I suppose every
> > time you encrypt the file, gpg will generate a new session key, so an
> > identical cleartext file will generate a completely different
> > cyphertext file every time.
> Yes, this is correct.
You probably ought to use the --whole-file option of rsync then because
the rolling checksums are only going to slow you down.
n Wed, Mar 20, 2002 at 05:22:46PM -0800, Martin Pool wrote:
> On 20 Mar 2002, jeremy bornstein <uke at jeremy.org> wrote:
> > Dave Dykstra wrote:
> > > Wouldn't encrypting the file with gpg change the timestamp as well as the
> > > size, so rsync would still copy the file?
> > It certainly does--which is why I reset it afterwards.
> > Although the backup script I use is pretty simple, having this patch
> > to rsync does not obviate it. I actually call rsync twice--once to
> > determine the list of files to be transferred, and once to transfer
> > the encrypted files. In-between I do the actual encryption (and
> > munging of the mod dates).
> Oh, do you mean you fiddle the mtimes of the source files to be the same
> as those of the destination files, and you want rsync to therefore
> not transfer them?
> Rather than going to all that trouble, why not just have your script
> produce an exclude file?
Yes, and use --ignore-times to always transfer the files you select.
More information about the rsync