https://bugzilla.samba.org/show_bug.cgi?id=11481
--- Comment #7 from Paul N ---
(Sorry, more...)
The greatest sin of how --ignore-errors misbehaves in the above case is that
the only error REPORTED at the end of the transfer is the one for the oversized
file that caused the problem... so a bunch
https://bugzilla.samba.org/show_bug.cgi?id=11481
--- Comment #6 from Paul N ---
Slightly correction to my above comment, implying 1-2 more bugs:
- When --ignore-errors is not specified, all subsequent files fail with
'Operation not permitted (1)', which is incorrect, at least at the environment
https://bugzilla.samba.org/show_bug.cgi?id=11481
--- Comment #5 from sambab...@phox.ca ---
@Kevin, your understanding here is incorrect: rsync bails entire transfers on
things that are NOT fatal to the entire transfer, and --ignore-errors overrides
this. I ended up stumbling upon this bug as a r
https://bugzilla.samba.org/show_bug.cgi?id=11481
Wayne Davison changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #4 from Wayne Davi
https://bugzilla.samba.org/show_bug.cgi?id=11481
--- Comment #2 from Muralidhar N ---
Yes. we must have --ignore-errors independent of --delete and also --force
independent of --delete. sometimes we may not use --delete at all and want to
continue with rsync even when errors are there and also so
https://bugzilla.samba.org/show_bug.cgi?id=11481
--- Comment #3 from Kevin Korb ---
Rsync does continue on errors unless those errors are fatal (like a failure to
connect). Sounds more like what you want is a retry option which is easy
enough to script.
--
You are receiving this mail because:
https://bugzilla.samba.org/show_bug.cgi?id=11481
--- Comment #1 from Kevin Korb ---
--force exists to force --delete to work even when there are errors. That is
the only behaviour that rsync changes based on errors. So what would you
expect --ignore-errors to change when there is no --delete?
