> the original message.
>
>
> From: rsync [rsync-boun...@lists.samba.org] on behalf of Kevin Korb via rsync
> [rsync@lists.samba.org]
> Sent: Thursday, March 23, 2017 1:10 PM
> To: rsync@lists.samba.org
> Subject: Re: rsync: "-c
org
Subject: Re: rsync: "-c" option clarification
Before anyone yells at me, yes, you can use rsync's --checksum to detect
(and fix) files that are incorrect despite having correct timestamps and
sizes. This would mean that a previous rsync had been corrupted not the
current one. Bu
Before anyone yells at me, yes, you can use rsync's --checksum to detect
(and fix) files that are incorrect despite having correct timestamps and
sizes. This would mean that a previous rsync had been corrupted not the
current one. But it is important to note that this would only be
reported to yo
The -c option causes rsync to checksum EVERY file on both ends BEFORE
rsync does anything else. It checksums files that are on only 1 end.
It checksums files that are different sizes. It will not catch a
hardware problem preventing rsync from writing a file correctly.
On 03/23/2017 03:12 PM, ste
Hi
I am using "rsync" to send files from a source machine to a remote machine as
one typically does. I would like to clarify that the "-c" option will cause
the checksum on the receiving end to be created by reading the already written
file and NOT the data stream on the receiving end. This
