Janne Johansson <icepic...@gmail.com> wrote: > In practical terms, if I rsync a file from X to Y, and rsync says it is > complete, how to verify the 4G files actually are equal? > Given that rsync only knows that hash(A) was equal to hash(B) at the end, > what do you propose to use for verification?
In practical terms, it is indeed very unprobable that a file that passed the last check is not the right one. I answered first Andreas Gunnarsson, not Matthew Weigel who brought something new to the discussion. Can you figure why? Because, although my original question was about rsync and cvsync, it mutated to a discussion about programming praxis. And yes, it is relevant to OpenBSD, because programming of an Operating System is a very delicate thing and developers of OpenBSD have here a strange standpoint that they defend without sound argumentation, including asking the one that expresses the critics that he goes away. If you read rsync(1) and other documentation, you do not find any mention of the last check and backtracking, but you read: "Rsync is widely used for backups and mirroring and as an improved copy command for everyday use." This is like the first answer I got, from Kenneth R Westerback: "People use cvsync or rsync to create/maintain a local copy or copies of the repository. I use cvsync to sync one repository with an external source and then run cvsyncd on that box if I want repositories on other local machines." Or also like: "Coca Cola is healthy, most people in the World drink Coca Cola." Rodrigo.
