-NEWS for rsync 2.6.5 (UNRELEASED)
+NEWS for rsync 2.6.9 (unreleased)
Protocol: 29 (unchanged)
-Changes since 2.6.4:
-
- OUTPUT CHANGES:
-
- - Non-printable chars in filenames are now output using backslash-
- escaped characters rather than '?'s. Any non-printable character is
- output using 3 digits of octal (e.g. "\n" -> "\012"), and a backslash
- is now output as "\\". Rsync also uses your locale setting, which
- can make it treat fewer high-bit characters as non-printable.
-
- - If rsync received an empty file list when pulling files, it would
- output an "nothing to do" message and exit with a 0 (success) exit
- status, even if the remote rsync returned an error (it did not do
- this under the same conditions when pushing files). This was changed
- to make the pulling behavior the same as the pushing behavior: we
- now do the normal end-of-run outputting (depending on options) and
- exit with the appropriate exit status.
+Changes since 2.6.8:
BUG FIXES:
- - A crash bug was fixed when a daemon had its "path" set to "/", did
- not have chroot enabled, and used some anchored excludes in the
- rsyncd.conf file.
-
- - Fixed a bug in the transfer of a single file when -H is specified
- that might have caused an infinite loop or perhaps a crash.
-
- - Fixed a case where the generator might try to tweak the write
- permissions of a read-only directory in list-only mode.
-
- - If --compare-dest or --link-dest uses a locally-copied file as the
- basis for an updated version, log this better when --verbose or -i
- is in effect.
-
- - Fixed the accidental disabling of --backup during the --delete-after
- processing.
-
- - Restored the ability to use the --address option in client mode (in
- addition to its use in daemon mode).
-
- - Make sure that some temporary progress information from the delete
- processing does not get left on the screen when it is followed by a
- newline.
-
- - When --existing skips a directory with extra verbosity, don't refer
- to it as a "file".
-
- - When transferring a single file to a different-named file, any
- generator messages that are source-file related no longer refer to
- the file by the destination filename.
-
- - Fixed a bug where hard-linking a group of files might fail if the
- generator hasn't created the destination directory yet.
-
- - Fixed a bug where a hard-linked group of files that is newly-linked
- to a file in a --link-dest dir doesn't link the files from the rest
- of the cluster.
-
- - When deleting files with the --one-file-system (-x) option set, rsync
- no longer tries to remove files from inside a mount-point on the
- receiving side.
-
- - Fixed a compatibility problem when using --cvs-ignore (-C) and
- sending files to an older rsync without using --delete.
-
- - Fixed the ommission of some directories in the delete processing when
- --relative (-R) was combined with a source path that had a trailing
- slash.
+ - If rsync is interrupted via a handled signal (such as SIGINT), it will
+ once again clean-up its temp file from the destination dir.
+
+ - An rsync daemon that is receiving files with "use chroot = no" no longer
+ sanitizes the symlink target strings (by default). This means that each
+ symlink's value will now be accepted (and thus returned) with its symlink
+ info intact. Also, in order to keep things safe, all arg paths and any
+ dereferenced symlinks (e.g. via --copy-links or --keep-dirlinks) are
+ manually verified to ensure that no symlinks try to escape past the top
+ of the module's path. These changes make a non-chroot daemon behave the
+ same way as a chroot daemon with regard to symlinks, and also avoids a
+ potential problem where a pre-existing symlink could have escaped the
+ module's hierarchy. See also the new "munge symlinks" daemon setting.
+
+ - 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.
+
+ - 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.)
+
+ - 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.
+
+ - 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 --only-write-batch=FILE option that may be used (instead
- of --write-batch=FILE) to create a batch file without doing any
- actual updating of the destination. This allows you to divert all
- the file-updating data away from a slow data link (as long as you
- are pushing the data to the remote server when creating the batch).
-
- - When the generator is taking a long time to fill up its output buffer
- (e.g. if the transferred files are few, small, or missing), it now
- periodically flushes the output buffer so that the sender/receiver
- can get started on the files sooner rather than later.
-
- - Improved the auth-errors that are logged by the daemon to include
- some information on why the authorization failed (wrong user,
- password mismatch, etc.). (The client-visible message is unchanged.)
-
- - Improved the client's handling of an "@ERROR" from a daemon so that
- it does not complain about an unexpectedly closed socket (since we
- really did expect the socket to close).
+ - 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 the daemon can't open the log-file specified in rsyncd.conf, fall
- back to using syslog. This is better than a (typically) totally
- silent failure (since a daemon is not usually run with --no-detach).
+ - 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.)
- - The man pages now consistently refer to an rsync daemon as a "daemon"
- to distinguish it from a server in a non-daemon transfer.
+ - Made "log file" and "syslog facility" settable on a per-module basis in
+ the daemon's config file.
- INTERNAL:
+ - Added the "munge symlinks" daemon setting to enable the old-style
+ tweaking of "unsafe" symlinks, but it can now be consistently applied
+ regardless of how "use chroot" is set.
- - Rsync now calls setlocale(LC_CTYPE, "").
+ - 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.)
- BUILD CHANGES:
+ - 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.
- - Fixed a bug in the SUPPORT{,_HARD}_LINKS defines which prevented
- rsync from being built without symlink or hard-link support.
+ DEVELOPER RELATED:
- - You can use --disable-locale to turn off any use of setlocale().
+ - 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.
- - Configure now disables the use of mkstemp() under HP-UX (since they
- refuse to fix its broken handling of large files).
+ - Updated config.guess and config.sub to their 2006-02-23 version.
- - Configure now explicitly checks for the lseek64() function so that
- the code can use HAVE_LSEEK64 instead of inferring lseek64()'s
- presence based on the presence of the off64_t type.
+ - Updated various files to include the latest FSF address and to have
+ consistent opening comments.