-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:
- - Fixed a really old bug that caused --checksum (-c) to checksum all the
- files encountered during the delete scan (ouch).
-
- - Made hard-links work with symlinks and devices again.
-
- - If a device-file/special-file changes permissions, rsync now updates the
- permissions without recreating the file.
-
- - 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.
-
- - 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.
-
- - Reject the combination of --inplace and --sparse since the sparse-output
- algorithm doesn't work when overwriting existing data.
-
- - Fixed the directory name in the error that is output when pop_dir()
- fails.
-
- - Really fixed the parsing of a "!" entry in .cvsignore files this time.
-
- - If the generator gets a stat() error on a file, output it (this used to
- require at least -vv for the error to be seen).
-
- - If waitpid() fails or the child rsync didn't exit cleanly, we now handle
- the exit status properly and generate a better error.
+ - An rsync daemon that is receiving files with "use chroot = no" no longer
+ sanitizes the symlink target strings. 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, any option that tells a
+ non-chroot daemon to treat some symlinks as their referent (such as
+ --copy-links or --keep-dirlinks) now manually checks the symlink chain
+ to ensure that the symlinks do not try to escape past the top of the
+ module's path. Both these changes make a non-chroot daemon behave the
+ same 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.
+
+ - Fixed a overzealous sanitizing bug in the handling of the --*-dest
+ options (--link-dest, --copy-dest, and --compare-dest): 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.)
+
+ - Make sure that the --link-dest option can still do its job even when -I
+ or --size-only is specified.
+
+ - 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).
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 --min-size=SIZE option to exclude small files from the
- transfer.
-
- - Added the --compress-level option to allow you to set how aggressive
- rsync's compression should be (this option implies --compress).
-
- - Enhanced the parsing of the SIZE value for --min-size and --max-size
- to allow easy entry of multiples of 1000 (instead of just multiples
- of 1024) and off-by-one values too (e.g. --max-size=8mb-1).
-
- - The options --human-readable (-h) and --si change the output of the
- --stats and the end-of-run summary to be easier to read.
-
- - If lutimes() and/or lchmod() are around, use them to allow the
- preservation of attributes on symlinks.
-
- - 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. (See the manpage for a list of the environment variables
- that are set with information about the transfer.)
-
- - 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 will now 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 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 the --chmod=MODE option that allows the destination permissions
- to be changed from the source permissions. E.g. --chmod=g+w,o-rwx
-
- - Allow the --temp-dir option to be specified when starting a daemon,
- which sets the default temporary directory for incoming files.
-
- - If --delete is combined with --dirs without --recursive, rsync will
- now delete in any directory whose content is being synchronized.
-
- - The file-count stats that are output by --progress were improved to
- better indicate what the numbers mean. For instance, the output:
- "(xfer#5, to-check=8383/9999)" indicates that this was transferred
- file #5, and we still need to check 8383 files out of 9999 total.
-
- - Some minor documentation improvements.
-
- - Updated some diffs in the patches dir.
-
- INTERNAL:
-
- - Some buffer sizes were expanded a bit, particularly on systems where
- MAXPATHLEN is overly small (e.g. cygwin).
-
- - If io_printf() tries to format more data than fits in the buffer, exit
- with an error instead of transmitting a truncated buffer.
-
- - If a va_copy macro is defined, lib/snprintf.c will use it when defining
- the VA_COPY macro.
-
- - Reduced the amount of stack memory needed for each level of directory
- recursion by nearly MAXPATHLEN bytes.
+ - ...
DEVELOPER RELATED:
- - Several diffs in the patches dir now use the proper --enable-FOO
- configure option instead of --with-FOO to turn on the inclusion of
- the newly patched feature.
+ - 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.
+
+ - Updated config.guess and config.sub to their 2006-02-23 version.
+ - Updated various files to include the latest FSF address and to have
+ consistent opening comments.