- - Added the --filter (-f) option and its helper option, -F. Filter
- rules are an extension to the existing include/exclude handling
- that also supports nested filter files as well as per-directory
- filter files (like .cvsignore, but with full filter-rule parsing).
- This new option was chosen in order to ensure that all existing
- include/exclude processing remained 100% compatible with older
- versions. Protocol 29 is needed for full filter-rule support, but
- backward-compatible rules work with earlier protocol versions.
- (Promoted from the patches dir and enhanced.)
-
- - Added the --delay-updates option that puts all updated files into
- a temporary directory (by default ".~tmp~", but settable via the
- --partial-dir=DIR option) until the end of the transfer. This
- makes the updates a little more atomic for a large transfer.
-
- - If rsync is put into the background, any output from --progress is
- reduced.
-
- - Documented the "max verbosity" setting for rsyncd.conf. (This
- setting was added a couple releases ago, but left undocumented.)
-
- - The sender and the generator now double-check the file-list index
- they are given, and refuse to try to do a file transfer on a
- non-file index (since that would indicate that something had gone
- very wrong).
-
- - Added the --itemize-changes (-i) option, which is a way to output a
- more detailed list of what files changed in any way and how they
- changed. The effect is the same as specifying a --log-format of
- "%i %n%L" (see the rsyncd.conf manpage). Works with --dry-run too.
-
- - Added the --fuzzy option, which attempts to find a basis file for a
- file that is being created from scratch. The current algorithm
- only looks in the destination directory for the created file, but
- it does attempt to find a match based on size/mod-time (in case the
- file was renamed with no other changes) as well as based on a fuzzy
- name-matching algorithm. This option requires protocol 29 because
- it needs the new file-sorting order. (Promoted from patches dir
- and enhanced.) (Requires protocol 29.)
-
- - Added the --remove-sent-files option, which lets you move files
- between systems.
-
- - The hostname in HOST:PATH or HOST::PATH may now be an IPv6 literal
- enclosed in '[' and ']' (e.g. "[::1]"). (We already allowed IPv6
- literals in the rsync://HOST:PORT/PATH format.)
-
- - When rsync recurses to build the file list, it no longer keeps open
- the directory handles of all the parent dirs inside the transfer.
-
- - When building under windows, the default for --daemon is now to
- avoid detaching, requiring the new --detach option to force rsync
- to detach.
-
- - The --dry-run option can now be combined with either --write-batch or
- --read-batch, allowing you to run a do-nothing test command to see
- what would happen without --dry-run.
-
- - Improved the option descriptions in the --help text.
-
- SUPPORT FILES:
-
- - Added atomic-rsync to the support dir: a perl script that will
- transfer some files using rsync, and then move the updated files into
- place all at once at the end of the transfer. Only works when
- pulling, and uses --link-dest and a parallel hierarchy of files to
- effect its update.
-
- - Added mnt-excl to the support dir: a perl script that takes the
- /proc/mounts file and translates it into a set of excludes that will
- exclude all mount points (even mapped mounts to the same disk). The
- excludes are made relative to the specified source dir and properly
- anchored.
-
- - Added savetransfer.c to the support dir: a C program that can make
- a copy of all the data that flows over the wire. This lets you test
- for data corruption (by saving the data on both the sending side and
- the receiving side) or provides a way to help debug a protocol error.
-
- - Added rrsync to the support dir: this is my version of Joe Smith's
- restricted rsync perl script. This helps to ensure that only certain
- rsync commands can be run by an ssh invocation.
-
- INTERNAL:
-
- - Added better checking of the checksum-header values that come over
- the socket.
-
- - Merged a variety of file-deleting functions into a single function so
- that it is easier to maintain.
-
- - Improved the type of some variables (particularly blocksize vars) for
- consistency and proper size.
-
- - Got rid of the uint64 type (which we didn't need).
-
- - Use a slightly more compatible set of core #include directives.
-
- - Defined int32 in a way that ensures that the build dies if we can't
- find a variable with at least 32 bits.
-
- - The daemon's "read only" config item now sets an internal read_only
- variable that makes extra sure that no write/delete calls on the
- read-only side can succeed.
-
- PROTOCOL DIFFERENCES FOR VERSION 29:
-
- - A 16-bit flag-word is transmitted after every file-list index. This
- indicates what is changing between the sender and the receiver. The
- generator now transmits an index and a flag-word to indicate when
- dirs and symlinks have changed (instead of producing a message),
- which makes the outputting of the information more consistent and
- less prone to screen corruption (because either the receiver or the
- sender is now outputting all the file-change info).
-
- - If a file is being hard-linked, the appropriate bit is enabled in
- the flag-word and the name of the file that was linked immediately
- follows in vstring format (see below).
-
- - If a file is being transferred with an alternate-basis file, the
- appropriate bit is enabled in the flag-word and a single-byte
- follows, indicating what type of basis file was chosen. If that
- indicates that a fuzzy-match was selected, the name of the match
- immediately follows in vstring format. A vstring is a variable
- length string that has its size written prior to the string, and
- no terminating null. If the string is from 1-127 bytes, the length
- is a single byte. If it is from 128-32767 bytes, the length is
- written as ((len >> 8) | 0x80) followed by (len % 0x100).
-
- - The sending of exclude names is done using filter-rule syntax. This
- means that all names have a prefixed rule indicator, even excludes
- (which used to be sent as a bare pattern, when possible). The -C
- option will include the per-dir .cvsignore merge file in the list of
- filter rules so it is positioned correctly (unlike in some older
- transfer scenarios).
-
- - Rsync sorts the filename list in a different way: it sorts the subdir
- names after the non-subdir names for each dir's contents, and it
- always puts a dir's contents immediately after the dir's name in the
- list. (Previously an item named "foo.txt" would sort in between
- directory "foo/" and "foo/bar".)
-
- - When talking to a protocol 29 rsync daemon, a list-only request
- is able to note this before the options are sent over the wire and
- the new --list-only option is included in the options.
-
- - When the --stats bytes are sent over the wire (or stored in a batch),
- they now include two elapsed-time values: one for how long it took to
- build the file-list, and one for how long it took to send it over the
- wire (each expressed in thousandths of a second).
-
- - When --delete-excluded is specified with some filter excludes, a
- client sender will now initiate a send of the filter rules to the
- receiver (older protocols used to omit the sending of excludes in
- this situation since there were no receiver-specific rules that
- survived --delete-excluded back then). Note that, as with all the
- filter-list sending, only items that are significant to the other
- side will actually be sent over the wire, so the filter-rule list
- is often empty in this scenario.
-
- - A protocol-29 batch file includes a bit for the setting of the --dirs
- option. Also, the shell script created by --write-batch will use the
- --filter option instead of --exclude-from to capture any filter rules.
-
- - An index equal to the file-list count is sent as a keep-alive packet
- from the generator to the sender, which then forwards it on to the
- receiver. This normally invalid index is only a valid keep-alive
- packet if the 16-bit flag-word that follows it contains a single bit
- (ITEM_IS_NEW, which is normally an illegal flag to appear alone).