Storage compression patch for Rsync (unfinished)

jw schultz jw at
Mon Jan 27 02:20:01 EST 2003

On Sun, Jan 26, 2003 at 06:04:52PM -0800, Craig Barratt wrote:
> > Block checksums come from the receiver so cached block
> > checksums are only useful when sending to a server which had
> > better know it has block checksums cached.
> The first statement is true (block checksums come from the receiver),
> but the second doesn't follow.  I need to cover the case where the
> client is the receiver and the client is caching the checksums. That
> needs a command-line switch, since the server would otherwise use
> time(NULL) as the checksum seed, which is then sent from the server
> to the client at protocol startup.

OK.  I'll buy that as a possibility worth allowing for.
This can be another option like --server, --daemon and
--sender, neither discussed on the rsync manpage with normal
options nor listed in USAGE.  That will eliminate user

Someday we should probably get a writup that covers these
protocol oriented command-line options and succinctly
discusses the issues of what the sender and receiver do.
The whitepaper (i reviewd it recently) is nice for
describing the theory and all the math but the pertinant
implimentation issues are neglected.

	J.W. Schultz            Pegasystems Technologies
	email address:		jw at

		Remember Cernan and Schmitt

More information about the rsync mailing list