-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You aren't using -a or -t so rsync isn't copying timestamps so it has
no idea what has changed and what hasn't.
On 11/10/13 22:39, Felipe Alvarez wrote:
> rsync -b --suffix=.felipe /tmp/file1 /tmp/file2 remote_host:/tmp/
>
> If file1 has not changed,
rsync -b --suffix=.felipe /tmp/file1 /tmp/file2 remote_host:/tmp/
If file1 has not changed, I still get a /tmp/file1.felipe file which is
100% exactly the same as /tmp/file1
Can this be prevented, while still backing up files that have changed?
Cheers,
Felipe
--
Please use reply-all for most re
On Fri, Nov 1, 2013 at 2:12 PM, Carlos Carvalho wrote:
>
> There seems to be an overflow that's rarely triggered somewhere...
>
If you can get a backtrace of the crash, that'd be helpful; i.e. run an
rsync with debug symbols, and ensure that your core files aren't limited
for the rsync process (ul
On Mon, Oct 7, 2013 at 5:07 AM, thomas veymont wrote:
> yes : disabling the timeout on the server side worked around the problem.
> anyway, ready to test additional patches if helpful.
I have finally gotten a fix for this checked-in to git:
https://git.samba.org/?p=rsync.git;a=commitdiff;h=e461
