- Fixed an overzealous sanitizing bug in the handling of the --link-dest,
--copy-dest, and --compare-dest options to a daemon without chroot: if
the copy's destination dir is deeper than the top of the module's path,
- these options now accept a safe number of ../ (parent-dir) references
+ these options now accept a safe number of parent-dir (../) references
(since these options are relative to the destination dir). The old code
incorrectly chopped off all "../" prefixes for these options, no matter
how deep the destination directory was in the module's hierarchy.
process. (These problems could only affect an rsync daemon that was
receiving files.)
+ - Fixed a bug where using --dry-run with a --*-dest option with a path
+ relative to a directory that does not yet exist: the affected option
+ gets its proper path value so that the output of the dry-run is right.
+
- Fixed a bug in the %f logfile escape when receiving files: the
destination path is now included in the output (e.g. you can now tell
when a user specifies a subdir inside a module).
- If the receiving side fails to create a directory, it will now skip
trying to update everything that is inside that directory.
- - Make sure that the --link-dest option can still do its job even when -I
- is specified.
-
- If --link-dest is specified with --checksum but without --times, rsync
will now allow a hard-link to be created to a matching link-dest file
even when the file's modify-time doesn't match the server's file.
- Fixed a recent bug where an --exclude='*' could affect the root (/) of
the filesystem with --relative enabled.
+ - When --inplace creates a file, it is now created with owner read/write
+ permissions (0600) instead of no permissions at all. This avoids a
+ problem continuing a transfer that was interrupted (since --inplace
+ will not update a file that has no write permissions).
+
+ - If either --remove-source-files or --remove-sent-files is enabled and we
+ are unable to remove the source file, rsync now outputs an error.
+
+ - Fixed a bug in the daemon's "incoming chmod" rule: newly-created
+ directories no longer get the 'F' (file) rules applied to them.
+
ENHANCEMENTS:
- Added the --log-file=FILE and --log-file-format=FORMAT options. These
tweaking of "unsafe" symlinks, but it can now be consistently applied
regardless of how "use chroot" is set.
+ - Added the --remove-source-files option as a replacement for the (now
+ deprecated) --remove-sent-files option. This new option removes all
+ non-dirs from the source directories, even if the file was already
+ up-to-date. This fixes a problem where interrupting an rsync that
+ was using --remove-sent-files and restarting it could leave behind
+ a file that the earlier rsync synchronized, but didn't get to remove.
+ (The deprecated --remove-sent-files is still understood for now, and
+ still behaves in the same way as before.)
+
- Added a new environment variable to the pre-/post-xfer exec commands (in
the daemon's config file): RSYNC_PID. This value will be the same in
both the pre- and post-xfer commands, so it can be used if the pre-xfer