-NEWS for rsync 2.6.5 (UNRELEASED)
-Protocol: 29 (unchanged)
-Changes since 2.6.4:
+NEWS for rsync 3.0.0 (UNRELEASED)
+Protocol: 30 (changed)
+Changes since 2.6.9:
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 the output of -ii when combined with one of the --*-dest options:
+ it now itemizes all the items, not just the changed ones.
- - Fixed a case where the generator might try to tweak the write
- permissions of a read-only directory in list-only mode.
+ - 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.
- - 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.
+ - 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 the accidental disabling of --backup during the --delete-after
- processing.
+ - A negated filter rule now sends the negation option when sending the
+ filter rules.
- - Restored the ability to use the --address option in client mode (in
- addition to its use in daemon mode).
+ - Fixed a problem with the --out-format (aka --log-format) option: it
+ would output superfluous directory information for a non-daemon rsync.
- - 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.
+ - 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.
- - When --existing skips a directory with extra verbosity, don't refer
- to it as a "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.
- ENHANCEMENTS:
+ - Make sure that directory permissions of a newly-created destination
+ directory are handled right when --perms is left off.
- - 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).
+ ENHANCEMENTS:
- - Changed the outputting of "safe" filenames to use backslash-escaped
- characters rather than '?'s. Any non-printable character is output
- using octal (e.g. "\n" -> "\012"), and backslash is output as "\\".
+ - 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.
+
+ - 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).
- - 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.)
+ INTERNAL:
- - 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 some isType() functions that make dealing with signed characters
+ easier without forcing variables via casts.
- - 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).
+ - Upgraded the included popt version to 1.10.2 and improved its use of
+ string-handling functions.
- INTERNAL:
+ - Added missing prototypes for compatibility functions from the lib dir.
- - Rsync now calls setlocale(LC_CTYPE, "").
+ - Configure determines if iconv() has a const arg, allowing us to avoid a
+ compiler warning.
- BUILD CHANGES:
+ - Made the sending of some numbers more efficient for protocol 30.
- - Fixed a bug in the SUPPORT{,_HARD}_LINKS defines which prevented
- rsync from being built without symlink or hard-link support.
+ - Make sure that a daemon process doesn't mind if the client was weird and
+ omitted the --server option.
- - You can use --disable-locale to turn off any use of setlocale().
+ - Improved the use of "const" on pointers.
- - Configure now disables the use of mkstemp() under HP-UX (since they
- refuse to fix its broken handling of large files).
+ DEVELOPER RELATED:
- - 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.
+ - ...