relative path), the backup code was erroneously trying to backup a
file that was put into the partial-dir.
+ - If a file gets resent in a single transfer and the --backup option is
+ enabled along with --inplace, rsync no longer performs a duplicate
+ backup (it used to overwrite the first backup with the failed file).
+
- One call to flush_write_file() was not being checked for an error.
- The --no-relative option was not being sent from the client to a
is creating (e.g. dirs, symlinks) is now integrated into the progress
output without overlapping it. (Requires protocol 29.)
- - When --timeout is specified, lulls in the transfer while the
- generator scanning the file system (either looking for files to send
- or files to delete) now generate a new keep-alive packet that will
- keep the transfer going (as long as the generator continues to make
- progress). (Requires protocol 29.)
+ - When --timeout is specified, lulls that occur in the transfer while
+ the generator is doing work that does not generate socket traffic
+ (looking for changed files, deleting files, doing directory-time
+ touch-ups, etc.) will cause a new keep-alive packet to be sent that
+ should keep the transfer going as long as the generator continues to
+ make progress. (Requires protocol 29.)
- The stat size of a device is not added to the total file size of the
- items we encounter since it might be undefined on some OSes.
+ items in the transfer since the size might be undefined on some OSes.
ENHANCEMENTS:
- If --inplace is specified, the generator flags any transfer that is
using an alternate basis file so that the sender can use the entire
- file in the rsync algorithm (unlike a normal --inplace update).
+ basis file in the rsync algorithm (unlike a normal --inplace update).
- The sending of exclude names is done using filter-rule syntax. This
means that all names have a prefixed rule indicator, even excludes
--filter option instead of --exclude-from to capture any filter rules.
- An index equal to the file-list count is sent as a keep-alive packet
- from the generator to the sender, who then forwards it on to the
+ from the generator to the sender, which then forwards it on to the
receiver. This normally invalid index is only a valid keep-alive
packet if the 16-bit flag-word that follows it contains a single bit
(ITEM_IS_NEW, which is normally an illegal flag to appear alone).