-NEWS for rsync 2.6.1 (UNRELEASED)
-Protocol: 27 (unchanged)
-Changes since 2.6.0:
-
- ENHANCEMENTS:
-
- * Lower memory use and more optimal transfer of data over
- the socket (see the INTERNAL section for details).
-
- * The RSYNC_PROXY environment variable can now contain a
- "USER:PASS@" prefix before the "HOST:PORT" information.
- (Bardur Arantsson)
-
- * The --progress output now mentions how far along in the
- transfer we are, including both a count of files transferred
- and a percentage of the total file-count that we're processed.
-
- * The configure script now accepts --with-rsyncd-conf=PATH
- to override the default value of the /etc/rsyncd.conf file.
+NEWS for rsync 3.0.0 (UNRELEASED)
+Protocol: 30 (changed)
+Changes since 2.6.9:
BUG FIXES:
- * 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.
-
- * Fixed the "refuse options" setting in the rsyncd.conf file.
-
- * Rsync no longer discards a double-slash at the start of a filename
- when trying to open the file. It also no longer constructs names
- that start with a double slash (unless the user supplied both).
-
- 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.
-
- * Dropped support for protocol versions less than 20
- (2.3.0 released 15 Mar 1999) and activated warnings for
- protocols less than 25 (2.5.0 released 23 Aug 2001)
- (Wayne Davison and J.W. Schultz, severally)
-
- * More optimal data transmission for --hard-links (protocol 28).
-
- * More optimal data transmission for --checksum (protocol 28).
+ - Fixed the output of -ii when combined with one of the --*-dest options:
+ it now itemizes all the items, not just the changed ones.
- * Less memory is used when --checksum is specified.
+ - Made the output of all file types consistent when using a --*-dest
+ option. Prior versions used to output too many creation events for
+ matching items.
- * Less memory is used in the file list (a per-file savings).
+ - The code that waits for a child pid now handles being interrupted by a
+ signal. This fixes a problem with the pre-xfer exec function not being
+ able to get the exit status from the script.
- * 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)
+ - A negated filter rule now sends the negation option when sending the
+ filter rules.
- * 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)
+ - Fixed a problem with the --out-format (aka --log-format) option: it
+ would output superfluous directory information for a non-daemon rsync.
- * 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.
+ - Fixed a problem with -vv (double --verbose) and --stats when "pushing"
+ files (which includes local copies). Version 2.6.9 would complete the
+ copy, but exit with an error when the receiver output its memory stats.
- * 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).
+ - If --password-file is used on a non-daemon transfer, rsync now complains
+ and exits. This should help users figure out that they can't use this
+ option to control a remote shell's password prompt.
- * 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:
+ - Make sure that directory permissions of a newly-created destination
+ directory are handled right when --perms is left off.
ENHANCEMENTS:
- * "ssh" is now the default remote shell for rsync. If you want to
- change this, configure like this: "./configure --with-rsh=rsh".
-
- * Added --files-from, --no-relative, --no-implied-dirs, and --from0.
- Note that --from0 affects the line-ending character for all the
- files read by the --*-from options. (Wayne Davison)
-
- * Length of csum2 is now per-file starting with protocol version
- 27. (J.W. Schultz)
-
- * Per-file dynamic block size is now sqrt(file length). The
- per-file checksum size is determined according to an algorithm
- provided by Donovan Baarda which reduces the probability of rsync
- algorithm corrupting data and falling back using the whole md4
- checksums. (J.W. Schultz, Donovan Baarda)
-
- * The --stats option no longer includes the (debug) malloc summary
- unless the verbose option was specified at least twice.
-
- * Added a new error/warning code for when files vanish from the
- sending side. Made vanished source files not interfere with the
- file-deletion pass when --delete-after was specified.
-
- * Various trailing-info sections are now preceded by a newline.
-
- BUG FIXES:
-
- * Fixed several exclude/include matching bugs when using wild-cards.
- This has a several user-visible effects, all of which make the
- matching more consistent and intuitive. This should hopefully not
- cause anyone problems since it makes the matching work more like
- what people are expecting. (Wayne Davison)
-
- - A pattern with a "**" no longer causes a "*" to match slashes.
- For example, with "/*/foo/**", "foo" must be 2 levels deep.
- [If your string has BOTH "*" and "**" wildcards, changing the
- "*" wildcards to "**" will provide the old behavior in all
- versions.]
-
- - "**/foo" now matches at the base of the transfer (like /foo
- does). [Use "/**/foo" to get the old behavior in all versions.]
-
- - A non-anchored wildcard term floats to match beyond the base of
- the transfer. E.g. "CVS/R*" matches at the end of the path,
- just like the non-wildcard term "CVS/Root" does. [Use "/CVS/R*"
- to get the old behavior in all versions.]
-
- - Including a "**" in the match term causes it to be matched
- against the entire path, not just the name portion, even if
- there aren't any interior slashes in the term. E.g. "foo**bar"
- would exclude "/path/foo-bar" (just like before) as well as
- "/foo-path/baz-bar" (unlike before). [Use "foo*bar" to get the
- old behavior in all versions.]
+ - A new incremental-recursion algorithm is now used when rsync is talking
+ to another 3.0.0 version. This starts the transfer going more quickly
+ (before all the files have been found), and requires much less memory.
+ See the --recursive option in the manpage for some restrictions.
+
+ - The default --delete algorithm is now --delete-during when talking to a
+ 3.x rsync. This is a faster scan than using --delete-before (which is
+ the default when talking to older rsync versions), and is compatible with
+ the new incremental recursion mode.
+
+ - Added the --delete-delay option, which is a more efficient way to delete
+ files at the end of the transfer without needing a separate delete pass.
+
+ - Added the --acls (-A) option to preserve Access Control Lists. This is
+ an improved version of the prior patch that was available. (If you need
+ to have backward compatibility with old, patched versions, the new
+ acls.diff patch that will add that.)
+
+ - Added the --xattrs (-X) option to preserver extended attributes. This is
+ an improved version of the prior patch that was available. (If you need
+ to have backward compatibility with old, patched versions, the new
+ xattrs.diff patch that will add that.)
+
+ - Added the --fake-super option that allows a non-super user to preserve
+ all attributes of a file by using a special extended-attribute idiom.
+ There is also an analogous "fake super" option for an rsync daemon.
+
+ - Added the --iconv option, which allows rsync to convert filenames from
+ one character-set to another during the transfer. The default is to make
+ this feature available as long as your system has iconv_open(). If
+ compilation fails, specify --disable-iconv to configure and rebuild. If
+ you want rsync to perform character-set conversions by default, you can
+ specify --enable-iconv=CONVERT_STRING with the default value for the
+ --iconv option that you wish to use. For example, --enable-iconv=. is a
+ good choice. See the rsync man page for an explanation of the --iconv
+ option's settings.
+
+ - You may specify --max-delete=0 to a 3.0.0 client as long as the receiving
+ side is at least version 3.0.0. This means that you can pull from an
+ older rsync with this option, but pushing to an older rsync will generate
+ an error. *Be sure to never specify a 0 value to an older rsync client,
+ or it will be silently ignored.*
+
+ - The --hard-link option now uses less memory on both the sending and
+ receiving side for all protocol versions. For protocol 30, the use of a
+ hashtable on the sending side allows us to more efficiently convey to the
+ receiver what files are linked together. This reduces the amount of data
+ sent over the socket by a considerable margin (rather than adding more
+ data), and limits the in-memory storage of the device+inode information
+ to just the sending side for the new protocol 30, or to the receiving
+ side when speaking an older protocol (note that older rsync versions kept
+ the device+inode information on both sides).
- * The exclude list specified in the daemon's config file is now
- properly applied to the pulled items no matter how deep the
- user's file-args are in the source tree. (Wayne Davison)
-
- * For protocol version >= 27, mdfour_tail() is called when the
- block size (including checksum_seed) is a multiple of 64.
- Previously it was not called, giving the wrong MD4 checksum.
- (Craig Barratt)
-
- * For protocol version >= 27, a 64 bit bit counter is used in
- mdfour.c as required by the RFC. Previously only a 32 bit bit
- counter was used, causing incorrect MD4 file checksums for
- file sizes >= 512MB - 4. (Craig Barratt)
-
- * Fixed a crash bug when interacting with older rsync versions and
- multiple files of the same name are destined for the same dir.
- (Wayne Davison)
-
- * Keep tmp names from overflowing MAXPATHLEN.
-
- * Make --link-dest honor the absence of -p, -o, and -g.
-
- * Made rsync treat a trailing slash in the destination in a more
- consistent manner.
-
- * Fixed file I/O error detection. (John Van Essen)
-
- * Fixed bogus "malformed address {hostname}" message in rsyncd log
- when checking IP address against hostnames from "hosts allow"
- and "hosts deny" parameters in config file.
-
- * Print heap statistics when verbose >= 2 instead of when >= 1.
-
- * Fixed a compression (-z) bug when syncing a mostly-matching file
- that contains already-compressed data. (Yasuoka Masahiko and
- Wayne Davison)
-
- * Fixed a bug in the --backup code that could cause deleted files
- to not get backed up.
-
- * When the backup code makes new directories, create them with mode
- 0700 instead of 0755 (since the directory permissions in the
- backup tree are not yet copied from the main tree).
+ INTERNAL:
- * Call setgroups() in a more portable manner.
+ - Rsync now supports the transfer of 64-bit timestamps (time_t values).
- * Improved file-related error messages to better indicate exactly
- what pathname failed. (Wayne Davison)
+ - Fixed a build problem with older (2.x) versions of gcc.
- * Fixed some bugs in the handling of --delete and --exclude when
- using the --relative (-R) option. (Wayne Davison)
+ - Added some isType() functions that make dealing with signed characters
+ easier without forcing variables via casts.
- * Fixed bug that prevented regular files from replacing
- special files and caused a directory in --link-dest or
- --compare-dest to block the creation of a file with the
- same path. A directory still cannot be replaced by a
- regular file unless --delete specified. (J.W. Schultz)
+ - Upgraded the included popt version to 1.10.2 and improved its use of
+ string-handling functions.
- * Detect and report when open or opendir succeed but read and
- readdir fail caused by network filesystem issues and truncated
- files. (David Norwood, Michael Brown, J.W. Schultz)
+ - Added missing prototypes for compatibility functions from the lib dir.
- * Added a fix that should give ssh time to restore the tty settings
- if the user presses Ctrl-C at an ssh password prompt.
+ - Configure determines if iconv() has a const arg, allowing us to avoid a
+ compiler warning.
- INTERNAL:
+ - Made the sending of some numbers more efficient for protocol 30.
- * Eliminated vestigial support for old versions that we stopped
- supporting. (J.W. Schultz)
+ - Make sure that a daemon process doesn't mind if the client was weird and
+ omitted the --server option.
- * Simplified some of the option-parsing code. (Wayne Davison)
+ - Improved the use of "const" on pointers.
- * Some cleanup made to the exclude code, as well as some new
- defines added to enhance readability. (Wayne Davison)
+ DEVELOPER RELATED:
- * Changed the protocol-version code so that it can interact at a
- lower protocol level than the maximum supported by both sides.
- Added an undocumented option, --protocol=N, to force the value
- we advertise to the other side (primarily for testing purposes).
- (Wayne Davison)
+ - Rsync now has a way of handling protocol-version changes during the
+ development of a new protocol version. This exchange of sub-version
+ info does not interfere with the {MIN,MAX}_PROTOCOL_VERSION checking
+ in older versions (which would be the case if every minor change made
+ to the protocol in CVS incremented the main PROTOCOL_VERSION value).