- * When -x (--one-file-system) is combined with -L (--copy-links)
- or --copy-unsafe-links, no symlinked files are skipped, even
- if the referant file is on a different filesystem.
-
- * The --link-dest code now works properly for a non-root user
- when the UIDs of the source and destination differ and -o was
- specified, and when the group of the source can't be used on
- the destination and -g was specified. (Wayne Davison)
-
- * Fixed a bug in the handling of -H (hard-links) that might
- cause the expanded PATH/NAME value of the current item to
- get overwritten (due to an expanded-name caching bug).
- (Wayne Davison)
-
- * We now reset the "new data has been sent" flag at the start
- of each file we send. This makes sure that an interrupted
- transfer with the --partial option set doesn't keep a shorter
- temp file than the current basis file when no new data has been
- transfered over the wire for that file. (Wayne Davison)
-
- * Fixed a byte-order problem in --batch-mode on big-endian
- machines. (Jay Fenlason)
-
- * Fixed configure bug when running "./configure --disable-ipv6".
- (Wayne Davison)
-
- * Fixed "make test" bug when build dir is not the source dir.
-
- * When using --cvs-exclude, the exclude items we get from a
- directory's .cvsignore file once again only affect that one
- directory (and not all following directories too).
-
- * When transferring a file that has group 0 with -g specified
- (typically via -a) and not enough privs to retain the group,
- rsync no longer complains about "chown" failing.
-
- * When specifying the USER@HOST: prefix for a file, the USER
- part can now contain an '@', if needed (i.e. the last '@'
- is used to find the HOST, not the first).
-
- * Fixed some bugs in the handling of group IDs for non-root
- users: (1) It properly handles a group that the sender didn't
- have a name for (it would previously skip changing the group
- on any files in that group). (2) If --numeric-ids is used,
- rsync no longer attempts to set groups that the user doesn't
- have the permission to set.
-
- INTERNAL:
-
- * Most of the I/O is now buffered, which results in a pretty
- large speedup when running under MS Windows. (Craig Barratt)
-
- * Optimizations to the name-handling/comparing code have made
- some significant reductions in user-CPU time for large file
- sets. (Wayne Davison)
-
- * Some variable-type cleanup that makes the code more consistent.
- (Wayne Davison)
-
- * Reduced memory requirements of hard link preservation.
- (J.W. Schultz)
-
- * Implemented a new algorithm for hard-link handling that speeds
- up the code significantly. (J.W. Schultz and Wayne Davison)
-
- * The --hard-link option now uses the first existing file in the
- group of linked files as the basis for the transfer. This
- prevents the sub-optimal transfer of a file's data when a new
- hardlink is added on the sending side and it sorts alphabetically
- earlier in the list than the files that are already present on the
- receiving side.
-
- * Got rid of support for protocol versions 17 and 18 (which are
- both over 6 years old). (Wayne Davison)
-
- * More optimal data transmission for --hard-links (protocol 28).
-
- * More optimal data transmission for --checksum (protocol 28).
-
- * Less memory is used when --checksum is specified.
-
- * Less memory is used in the file list (a per-file savings).
-
- * Changed hardlink info and file_struct + strings to use
- allocation pools. This reduces memory use for large
- filesets and permits freeing memory to the OS. (J.W. Schultz)
-
- * The 2 pipes used between the receiver and generator processes
- (which are forked on the same machine) were reduced to 1 pipe
- and the protocol improved so that (1) it is now impossible to
- have the "redo" pipe fill up and hang rsync, and (2) trailing
- messages from the receiver don't get lost on their way through
- the generator over to the sender (the latter mainly affected
- hard-link messages). (Wayne Davison)
-
- * The reading & writing of the file list in batch-mode is now
- handled by the same code that sends & receives the list over
- the wire. This makes it much easier to maintain.
-
- * Optimized the -x (--one-file-system) flag's handling of any
- mount-point directories we encounter (it no longer scans the
- contents of the mount-point dirs, just to throw away the data).
-
- * Improved the internal uid/gid code to be more portable and
- a little more optimized.
-
-\f
-NEWS for rsync 2.6.0 (1 Jan 2004)
-Protocol: 27 (changed)
-Changes since 2.5.7:
+ - 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.