<div class="gmail_quote">On Sun, Feb 1, 2009 at 1:41 PM, David L. Anselmi <span dir="ltr"><<a href="mailto:anselmi@anselmi.us">anselmi@anselmi.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Angelo Bertolli wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The problem with rsyncing an ever-growing mbox is that it always needs to be<br>
copied since it will always be different.<br>
</blockquote>
<br></div>
It always needs to be copied but only blocks that don't match are copied (in this case only the new data at the end of the file). Which is exactly what we want.<br>
</blockquote><div><br>So rdiff then?<br><br>Normally rsync doesn't compare the two files: it just compares the timestamps and sizes, then copies the whole file if they don't match. You can force a comparison check, but that usually takes even longer.<br>
<br>Maybe rdiff will copy just the changed blocks, but it will still have to perform the diff. Yeah, I know there's supposed to be some "magic" to efficiently do diffs over the net (maybe using checksums?)<br>
<br></div></div>