Re: Bug: rsync erroneously changes modification time

2017-06-14 Thread max.power--- via rsync
Ok, that clears things up. Thanks. Quoting Paul Slootman via rsync : On Mon 12 Jun 2017, max.power--- via rsync wrote: How exactly does rsync determine that the copy has the incorrect timestamp and not the source file? The source by definition is correct. Paul -- Please use reply-all

Re: Bug: rsync erroneously changes modification time

2017-06-11 Thread max.power--- via rsync
to correct the incorrect timestamps without even looking inside of the files. If you are not 100% sure your file data matches you should not be using --size-only. On 06/11/2017 09:28 AM, max.power--- via rsync wrote: When a file of same length already exists at the destination then the comm

Bug: rsync erroneously changes modification time

2017-06-11 Thread max.power--- via rsync
When a file of same length already exists at the destination then the command 'rsync --archive --size-only' (--archive is same as -rlptgoD) may change the modification time of the destination file even if no modification was made. Type the following commands in a terminal in order to reprod