-NEWS for rsync 2.6.9 (unreleased)
-Protocol: 29 (unchanged)
-Changes since 2.6.8:
+NEWS for rsync 3.0.0 (UNRELEASED)
+Protocol: 30 (changed)
+Changes since 2.6.9:
+
+ NOTABLE CHANGE IN BEHAVIOR:
+
+ - The handling of implied directories when using --relative has changed
+ to send them as directories (e.g. no implied dir is ever sent as a
+ symlink). This avoids unexpected behavior and should not adversely
+ affect most people. If you're one of those rare people who relied
+ upon having an implied dir be duplicated as a symlink, either specify
+ --keep-dirlinks or --no-implied-dirs.
BUG FIXES:
- - If rsync is interrupted via a handled signal (such as SIGINT), it will
- once again clean-up its temp file from the destination dir.
+ - Fixed the output of -ii when combined with one of the --*-dest options:
+ it now itemizes all the items, not just the changed ones.
- - 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.
+ - 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.
- - 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.)
+ - 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.
- - 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.
+ - A negated filter rule (with a '!' modifier) no longer loses the negation
+ when sending the filter rules to the remote rsync.
- - 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 a problem with the --out-format (aka --log-format) option %f: it
+ would output superfluous directory information for a non-daemon rsync.
- - If the receiving side fails to create a directory, it will now skip
- trying to update everything that is inside that directory.
+ - 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.
- - 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.
+ - 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.
- - 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).
+ - Make sure that directory permissions of a newly-created destination
+ directory are handled right when --perms is left off.
- - 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.
+ - The itemized output of a newly-created destination directory is now
+ output as a creation event, not a change event.
- - 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).
+ - Improved --hard-link so that more corner cases are handled correctly
+ when combined with options such as --link-dest and/or --ignore-existing.
- - Fixed a recent bug where --delete was not working when transferring from
- the root (/) of the filesystem with --relative enabled.
+ - The --append option no longer updates a file that has the same size.
- - Fixed a recent bug where an --exclude='*' could affect the root (/) of
- the filesystem with --relative enabled.
+ - Fixed a bug when combining --backup and --backup-dir with --inplace:
+ any missing backup directories are now created.
- - 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).
+ - Fixed a bug when using --backup and --inplace with --whole-file or
+ --read-batch: backup files are actually created now.
- - 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.
+ - Starting up an extra copy of an rsync daemon does not delete the pidfile
+ for the running daemon -- if the pidfile exists, the extra program will
+ exit with 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.
+ - The daemon pidfile is checked and created sooner in the startup sequence.
- - Fixed an infinite loop bug when a filter rule was rejected due to being
- overly long.
+ - If a daemon module's "path" value is not an absolute pathname, the code
+ now makes it absolute internally (making it work properly).
ENHANCEMENTS:
- - 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.
-
- - 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.)
-
- - Made "log file" and "syslog facility" settable on a per-module basis in
- the daemon's config file.
-
- - 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 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.
+ - A new incremental-recursion algorithm is now used when rsync is talking
+ to another 3.x 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.
+
+ - Lowered memory use in the non-incremental-recursion algorithm for typical
+ option values (usually saving from 21-29 bytes per file).
+
+ - 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.
+
+ - Rsync now allows multiple remote-source args to be specified rather than
+ having to rely on a special space-splitting side-effect of the remote-
+ shell. Additional remote args must specify the same host or have an
+ empty hostname, as seen here: :file1 ::module/file2. This means that
+ local use of brace expansion now works: rsync -av host:path/{f1,f2} .
+
+ - Added the --protect-args (-s) option, that tells rsync to send most of
+ the command-line args at the start of the transfer rather than as args
+ to the remote-shell command. This protects them from space-splitting,
+ and only interprets basic wildcard special shell characters (*?[).
+
+ - 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, and it even
+ supports OS X ACLs. (If you need to have backward compatibility with
+ old, patched versions of rsync, apply the acls.diff file from the patches
+ dir.)
+
+ - 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 of rsync, apply
+ the xattrs.diff file from the patches dir.)
+
+ - 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 then
+ 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 manpage for an
+ explanation of the --iconv option's settings.
+
+ - Added the --skip-compress=LIST option to override the default list of
+ file suffixes that will not be compressed when using --compress.
+
+ - The daemon's default for "dont compress" was extended to include:
+ *.7z *.mp[34] *.mov *.avi *.ogg *.jpg *.jpeg
+ The matching routine was also optimized to run more quickly.
+
+ - The --max-delete option now outputs a warning if it skipped any file
+ deletions, including a count of how many deletions were skipped. (Older
+ versions just silently stopped deleting things.)
+
+ - You may specify --max-delete=0 to a 3.0.0 client to request that it warn
+ about extraneous files without deleting anything. If you're not sure
+ what version the client is, you can use the less-obvious --max-delete=-1,
+ as both old and new versions will treat that as the same request (though
+ older versions don't warn).
+
+ - 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 filter rules now support a perishable ("p") modifier that marks rules
+ that should not have an effect in a directory that is being deleted. e.g.
+ -f '-p .svn/' would only affect "live" .svn directories.
+
+ - If we get an error setting the time on a symlink, we don't complain about
+ it anymore (since some operating systems don't support that, and it's not
+ that important).
+
+ - Protocol 30 now uses MD5 checksums instead of MD4.
+
+ - Changed the --append option to not checksum the existing data in the
+ destination file, which speeds up file appending.
+
+ - Added the --append-verify option, which works like the older --append
+ option (verifying the existing data in the destination file). For
+ compatibility with older rsync versions, any use of --append that is
+ talking protocol 29 or older will revert to the --append-verify method.
+
+ - Documented and extended the support for the RSYNC_CONNECT_PROG variable
+ that can be used to enhance the client side of a daemon connection.
+
+ - Improved the dashes and double-quotes in the nroff manpage output.
+
+ - We now support a lot more --no-OPTION override options.
INTERNAL:
- - Did a code audit using IBM's code checker program and made several
- changes, including: replacing most of the strcpy() and sprintf() calls
- with strlcpy(), snprintf(), and memcpy(); adding a 0-value to an enum
- that had been intermingling a literal 0 with the defined enum values.
+ - The file-list sorting algorithm now uses a sort that keeps any same-
+ named items in the same order as they were specified. This allows
+ rsync to always ensure that the first of the duplicates is the one
+ that will be included in the copy. The new sort was also faster
+ than the glibc version of qsort() and mergesort() in my testing.
- - Fixed a potential bug in f_name_cmp() when both the args are a
- top-level "." dir (which doesn't happen in normal operations).
+ - Rsync now supports the transfer of 64-bit timestamps (time_t values).
- - Changed exit_cleanup() so that it can never return instead of exit.
- The old code might return if it found the exit_cleanup() function
- was being called recursively. The new code segments the exit code
- so that any recursive calls move on to the next step of the exit
- processing.
+ - Fixed a build problem with older (2.x) versions of gcc.
- DEVELOPER RELATED:
+ - Added some isType() functions that make dealing with signed characters
+ easier without forcing variables via casts.
+
+ - Changed strcat/strcpy/sprintf function calls to use safer versions.
+
+ - Upgraded the included popt version to 1.10.2 and improved its use of
+ string-handling functions.
- - 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.
+ - Added missing prototypes for compatibility functions from the lib dir.
- - The rsync.yo and rsyncd.conf.yo files have been updated to work
- better with the latest yodl 2.x releases.
+ - Configure determines if iconv() has a const arg, allowing us to avoid a
+ compiler warning.
- - Updated config.guess and config.sub to their 2006-02-23 version.
+ - Made the sending of some numbers more efficient for protocol 30.
+
+ - Make sure that a daemon process doesn't mind if the client was weird and
+ omitted the --server option.
+
+ - Improved the use of "const" on pointers.
+
+ - Improved J.W.'s pool_alloc routines to add a way of freeing older
+ sections of a pool's memory.
+
+ DEVELOPER RELATED:
- - Updated various files to include the latest FSF address and to have
- consistent opening comments.
+ - Rsync is now licensed under the GPLv3 or later.
+
+ - When running the tests, we now put our per-test temp dirs into a sub-
+ directory named testtmp (which is created, if missing). This allows
+ someone to symlink the testtmp directory to another filesystem (which is
+ useful if the build dir's filesystem does not support ACLs and xattrs,
+ and another file system does).
+
+ - Rsync now has a way of handling protocol-version changes during the
+ development of a new protocol version. This causes any out-of-sync
+ versions to speak an older protocol rather than fail in a cryptic manner.
+ This addition makes it safe to deploy a pre-release version that may
+ interact with the public. This new exchange of sub-version info does not
+ interfere with the {MIN,MAX}_PROTOCOL_VERSION checking algorithm (which
+ does not have enough range to allow the main protocol number to be
+ incremented for every minor tweak in that happens during development).