Protocol: 30 (changed)
Changes since 2.6.9:
- USER-VISIBLE CHANGES:
-
- - 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.
+ NOTABLE CHANGES 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, you should specify the transfer
+ of the symlink and the transfer of the referent directory as separate
+ args. (See also --keep-dirlinks and --no-implied-dirs.)
+
+ - Requesting a remote file list without specifying -r (--recursive) now
+ sends the -d (--dirs) option to the remote rsync rather than sending -r
+ along with an extra exclude of /*/*. If the remote rsync does not
+ understand the -d option (i.e. it is 2.6.3 or older), you will need to
+ either turn off -d (--no-d), or specify -r --exclude='/*/*' manually.
BUG FIXES:
- Fixed a bug when using --backup and --inplace with --whole-file or
--read-batch: backup files are actually created now.
+ - 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.
+
+ - The daemon pidfile is checked and created sooner in the startup sequence.
+
+ - If a daemon module's "path" value is not an absolute pathname, the code
+ now makes it absolute internally (making it work properly).
+
ENHANCEMENTS:
- A new incremental-recursion algorithm is now used when rsync is talking
(before all the files have been found), and requires much less memory.
See the --recursive option in the manpage for some restrictions.
- - Saved memory in the non-incremental-recursion algorithm for typical
+ - 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
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.
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
+ "--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 of the default list of
+ - 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:
that should not have an effect in a directory that is being deleted. e.g.
-f '-p .svn/' would only affect "live" .svn directories.
- - We now support a lot more --no-OPTION override options.
-
- 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).
- - Improved the dashes and double-quotes in the nroff manpage output.
-
- Protocol 30 now uses MD5 checksums instead of MD4.
- - If a daemon module's "path" value is not an absolute pathname, make it
- absolute.
-
- Changed the --append option to not checksum the existing data in the
destination file, which speeds up file appending.
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 rsync's daemon mode.
+ that can be used to enhance the client side of a daemon connection.
- - 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 other (non-wildcard) special shell characters.
+ - Improved the dashes and double-quotes in the nroff manpage output.
- - 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 no
- hostname.)
+ - We now support a lot more --no-OPTION override options.
INTERNAL:
and another file system does).
- 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 (since we'd quickly exceed the MAX_PROTOCOL_VERSION
- if we incremented the main PROTOCOL_VERSION value for every minor
- change during development).
+ 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).
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff