Re: Bug: rsync erroneously changes modification time

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 --

Re: Bug: rsync erroneously changes modification time

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 for most replies to avoid omitting the mailing list. To unsubscribe or

Re: Bug: rsync erroneously changes modification time

At 08:11 12.06.2017, max.power--- via rsync wrote: >Content-Transfer-Encoding: 7bit >Content-Disposition: inline > >How exactly does rsync determine that the copy has the incorrect >timestamp and not the source file? >Does it assume that the copy must be incorrect or are there other >criteria

Re: Bug: rsync erroneously changes modification time

How exactly does rsync determine that the copy has the incorrect timestamp and not the source file? Does it assume that the copy must be incorrect or are there other criteria that have to be considered? Quoting Kevin Korb via rsync : Whenever you use --times

Re: Bug: rsync erroneously changes modification time

Whenever you use --times (included in --archive) rsync will fix incorrect time stamps. The only thing --size-only is doing is keeping the incorrect data instead of replacing it. The purpose of these options is to "fix" a copy done in a way that did not preserve timestamps but the data is known

Bug: rsync erroneously changes modification time

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