- - 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).
-
- - When the generator is taking a long time to fill up its output buffer
- (e.g. if the transferred files are few, small, or missing), it now
- periodically flushes the output buffer so that the sender/receiver
- can get started on the files sooner rather than later.
-
- - 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.)
-
- - 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).
-
- - If the daemon can't open the log-file specified in rsyncd.conf, fall
- back to using syslog (and log an appropriate warning). This is
- better than what was typically a totally silent failure (since a
- daemon is not usually run with the --no-detach option that was
- necessary to see the error on stderr).
-
- - The man pages now consistently refer to an rsync daemon as a "daemon"
- to distinguish it from a server in a non-daemon transfer.
-
- - Made a small change to the rrsync script (restricted rsync -- in the
- support dir) to make a read-only server reject all --remove-* options
- when sending files (to future-proof it against the possibility of
- other similar options being added at some point).
+ - 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, and
+ moves the in-memory storage of the device+inode information from the
+ receiving side (for protocols < 30) to the sending side (note that
+ older rsync versions kept the device+inode information on both
+ sides).