Skip source files that differ from existing destination files with a warning?

Wayne Davison wayne at
Wed Sep 23 16:39:39 UTC 2020

On Thu, Sep 17, 2020 at 5:32 AM Matt McCutchen wrote:

> For the "not transfer" part, I can use --ignore-existing, but I don't see
> a direct way to be warned only about source files that differ from
> existing destination files.

Indeed, the 2-step approach that you mentioned is all that the released
rsync supports.  I've just checked-in a change that adds the `--info=skip2`
option that will add a suffix to the "exists" message that indicates the
existence-skipped file's status: "type change", or "sum change" (requires
`-c`), "file change" (based on quick check), "attr change", or "uptodate".

My reading of the code also suggests that if the sender is
> malicious, --ignore-existing will not stop the receiver from processing a
> transfer of an existing destination file initiated by the sender

Undoubtedly true, since the only thing the option does is limit what files
the generator will request. At some point it will be good to double-check
that the receiver doesn't get a file that the generator didn't request, but
the current nature of the round-robin pipe through the sender makes that
difficult without some new kind of direct generator-to-receiver flow of
information.  I have an idea of how I'd like to improve rsync's
receiver-side process setup in the future, but it's not easy to tweak in
the current version.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the rsync mailing list