forked from TrueCloudLab/rclone
44637dcd7f
Before this change, bisync had no ability to retry in the event of sync errors. After this change, bisync will retry if --resilient is passed, but only in one direction at a time. We can safely retry in one direction because the source is still intact, even if the dest was left in a messy state. If the first direction still fails after our final retry, we abort and do NOT continue in the other direction, to prevent the messy dest from polluting the source. If the first direction succeeds, we do then allow retries in the other direction. The number of retries is controllable by --retries (default 3) bisync: high-level retries if --resilient Before this change, bisync had no ability to retry in the event of sync errors. After this change, bisync will retry if --resilient is passed, but only in one direction at a time. We can safely retry in one direction because the source is still intact, even if the dest was left in a messy state. If the first direction still fails after our final retry, we abort and do NOT continue in the other direction, to prevent the messy dest from polluting the source. If the first direction succeeds, we do then allow retries in the other direction. The number of retries is controllable by --retries (default 3) |
||
|---|---|---|
| .. | ||
| bilib | ||
| testdata | ||
| bisync_test.go | ||
| cmd.go | ||
| deltas.go | ||
| help.go | ||
| LICENSE.cjnaz | ||
| listing.go | ||
| log.go | ||
| march.go | ||
| operations.go | ||
| queue.go | ||
| rc.go | ||