It depends on when it is changing. If the file changes during transfer,
the final checksum DOES trigger a resend of the changes (I've tested this
by syncing a large file over a slow link and changing the contents of the
source file during transfer).
If the change is still being written during the final checksum, then I
assume there is a risk of getting corrupted data. In practice, however, I
have not seen this happen.
I use rsync to pull DNS zone files to servers all over the world from a
central database. I have some other checks in place to reasonably assure
the files are not changing, but I have never had any corruption of data.
-Lee
---begin quoted text---
> Reply-To: [EMAIL PROTECTED]
> Originator: [EMAIL PROTECTED]
> From: Brian Whittaker <[EMAIL PROTECTED]>
> To: Multiple recipients of list RSYNC <[EMAIL PROTECTED]>
> Subject: Re: What happens when rsync is backing up volatile files?
> X-Listprocessor-Version: 6.0d -- ListProcessor by Anastasios Kotsikonas
> X-URL: http://lists.samba.org/
> X-Comment: Discussion of rsync package
> X-Mailer: Mozilla 4.7 [en] (Win95; I)
> Date: Fri, 30 Jun 2000 23:32:33 +1000
>
> It doesn't fall over. I'm not sure if the file ends up corrupted
> because there is code in rsync which does an overall checksum on what it
> writes into the new copy of the file and appears to be intended to
> trigger a resend if the checksum is not as expected. I've no idea if
> the resending actually works or not.
>
> Brian
>
> James Jones wrote:
> >
> > I'm sorry -- this is so tedious. I know this question gets asked all
> > the time but I can't find the relevant e-mails. So here goes with the
> > lazy approach.
> >
> > What happens if a file changes as it is being copied by rsync?
> > Does rsync fallover or is the file simply corrupted in transfer?
> >
> > Cheers and apologies,
> >
> > James
---end quoted text---
--
Lee Eakin - [EMAIL PROTECTED] - Naming Services, Texas Instruments -o)
[ permanent e-mail: [EMAIL PROTECTED] ] /\\
_\_v
The web is popular, but e-mail is still the "killer app."
--Vin McLellan <[EMAIL PROTECTED]>
