-NEWS for rsync 2.6.7 (UNRELEASED)
+NEWS for rsync 2.6.9 (unreleased)
Protocol: 29 (unchanged)
-Changes since 2.6.6:
+Changes since 2.6.8:
BUG FIXES:
- - Made hard-links work with symlinks and devices again.
+ - If rsync is interrupted via a handled signal (such as SIGINT), it will
+ once again clean-up its temp file from the destination dir.
- - If a device-file/special-file changes permissions, rsync now updates the
- permissions without recreating the file.
+ - 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
+ (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.
- - If the user specifies a remote-host for both the source and destination,
- we now output a syntax error rather than trying to open the destination
- hostspec as a filename.
+ - Fixed a bug where a deferred info/error/log message could get sent
+ directly to the sender instead of being handled by rwrite() in the
+ generator. This fixes an "unexpected tag 3" fatal error, and should
+ also fix a potential problem where a deferred info/error message from
+ the receiver might bypass the log file and get sent only to the client
+ process. (These problems could only affect an rsync daemon that was
+ receiving files.)
- - When --inplace creates a new destination file, rsync now creates it with
- permissions 0600 instead of 0000 -- this makes restarting possible when
- the transfer gets interrupted in the middle of sending a new file.
+ - 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.
- - Reject the combination of --inplace and --sparse since the sparse-output
- algorithm doesn't work when overwriting existing data.
+ - 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).
- - Fixed the directory name in the error that is output when pop_dir()
- fails.
+ - If the receiving side fails to create a directory, it will now skip
+ trying to update everything that is inside that directory.
+
+ - 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.
+
+ - The daemon now calls more timezone-using functions prior to doing a
+ chroot. This should help some C libraries to generate proper timestamps
+ from inside a chrooted daemon (and to not try to access /etc/timezone
+ over and over again).
+
+ - Fixed a bug in the handling of an absolute --partial-dir=ABS_PATH option:
+ it now deletes an alternate basis file from the partial-dir that was used
+ to successfully update a destination file.
+
+ - Fixed a bug in the handling of --delete-excluded when using a per-dir
+ merge file: the merge file is now honored on the receiving side, and
+ only its unqualified include/exclude commands are ignored (just as is
+ done for global include/excludes).
+
+ - Fixed a recent bug where --delete was not working when transferring from
+ the root (/) of the filesystem with --relative enabled.
+
+ - 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 --append option that makes rsync append data onto files
- that are longer on the source than the destination (this includes new
- files).
+ - Added the --log-file=FILE and --log-file-format=FORMAT options. These
+ can be used to tell any rsync to output what it is doing to a log file.
+ They work with a client rsync, a non-daemon server rsync (see the man
+ page for instructions), and also allows the overriding of rsyncd.conf
+ settings when starting a daemon.
- - If lutimes() and/or lchmod() are around, use them to allow the
- preservation of attributes on symlinks.
+ - The --log-format option was renamed to be --out-format to avoid confusing
+ it with affecting the log-file output. (The old option remains as an
+ alias for the new to preserve backward compatibility.)
- - Added two config items to the rsyncd.conf parsing: "pre-xfer exec"
- and "post-xfer exec". These allow a command to be specified on a
- per-module basis that will be run before and/or after a daemon-mode
- transfer.
+ - Made "log file" and "syslog facility" settable on a per-module basis in
+ the daemon's config file.
- - When using the --relative option, you can now insert a dot dir in
- the source path to indicate where the replication of the source dirs
- should start. For example, if you specify a source path of
- rsync://host/module/foo/bar/./baz/dir with -R, rsync would only
- replicate the "baz/dir" part of the source path (note: a trailing
- dot dir is unaffected unless it also has a trailing slash).
+ - 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 some new --no-FOO options that make it easier to override
- unwanted implied or default options. For example, "-a --no-o" (aka
- "--archive --no-owner") can be used to turn off the preservation of
- file ownership that is implied by -a.
+ - 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
+ command wants to cache some arg/request info for the post-xfer command.
- - Allow the --temp-dir option to be specified when starting a daemon,
- which sets the default temporary directory for incoming files.
+ DEVELOPER RELATED:
- INTERNAL:
+ - The acls.diff and xattrs.diff patches have received a bunch of work to
+ make them much closer to being acceptable in the main distribution.
- - Some buffer sizes were expanded a bit, particularly on systems where
- MAXPATHLEN is overly small (e.g. cygwin).
+ - Updated config.guess and config.sub to their 2006-02-23 version.
- - If io_printf() tries to format more data than fits in the buffer, exit
- with an error instead of transmitting a truncated buffer.
+ - Updated various files to include the latest FSF address and to have
+ consistent opening comments.
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff