+NEWS for rsync 2.6.8 (22 Apr 2006)
+Protocol: 29 (unchanged)
+Changes since 2.6.7:
+
+ BUG FIXES:
+
+ - Fixed a bug in the exclude code where an anchored exclude without any
+ wildcards fails to match an absolute source arg, but only when --relative
+ is in effect.
+
+ - Improved the I/O code for the generator to fix a potential hang when the
+ receiver gets an EOF on the socket but the generator's select() call
+ never indicates that the socket is writable for it to be notified about
+ the EOF. (This can happen when using stunnel).
+
+ - Fixed a problem with the file-reading code where a failed read (such as
+ that caused by a bad sector) would not advance the file's read-position
+ beyond the failed read's data.
+
+ - Fixed a logging bug where the "log file" directive was not being honored
+ in a single-use daemon (one spawned by a remote-shell connection or by
+ init).
+
+ - If rsync cannot honor the --delete option, we output an error and exit
+ instead of silently ignoring the option.
+
+ - Fixed a bug in the --link-dest code that prevented special files (such as
+ fifos) from being linked.
+
+ - The ability to hard-link symlinks and special files is now determined at
+ configure time instead of at runtime. This fixes a bug with --link-dest
+ creating a hard-link to a symlink's referent on a BSD system.
+
+ ENHANCEMENTS:
+
+ - In daemon mode, if rsync fails to bind to the requested port, the
+ error(s) returned by socket() and/or bind() are now logged.
+
+ - When we output a fatal error, we now output the version of rsync in the
+ message.
+
+ - Improved the documentation for the --owner and --group options.
+
+ - The rsyncstats script in "support" has an improved line-parsing regex
+ that is easier to read and also makes it to parse syslog-generated lines.
+
+ - A new script in "support": file-attr-restore, can be used to restore the
+ attributes of a file-set (the permissions, ownership, and group info)
+ taken from the cached output of a "find ARG... -ls" command.
+
+ DEVELOPER RELATED:
+
+ - Removed the unused function write_int_named(), the unused variable
+ io_read_phase, and the rarely used variable io_write_phase. This also
+ elides the confusing 'phase "unknown"' part of one error message.
+
+ - Removed two unused configure checks and two related (also unused)
+ compatibility functions.
+
+ - The xattrs.diff patch received a security fix that prevents a potential
+ buffer overflow in the receive_xattr() code.
+
+ - The acls.diff patch has been improved quite a bit, with more to come.
+
+ - A new patch was added: log-file.diff. This contains an early version of
+ a future option, --log-file=FILE, that will allow any rsync to log its
+ actions to a file (something that only a daemon supports at present).
+
+\f
+NEWS for rsync 2.6.7 (11 Mar 2006)
+Protocol: 29 (unchanged)
+Changes since 2.6.6:
+
+ OUTPUT CHANGES:
+
+ - The letter 'D' in the itemized output was being used for both devices
+ (character or block) as well as other special files (such as fifos and
+ named sockets). This has changed to separate non-device special files
+ under the 'S' designation (e.g. "cS+++++++ path/fifo"). See also the
+ "--specials" option, below.
+
+ - The way rsync escapes unreadable characters has changed. First, rsync
+ now has support for recognizing valid multibyte character sequences in
+ your current locale, allowing it to escape fewer characters than before
+ for a locale such as UTF-8. Second, it now uses an escape idiom of
+ "\#123", which is the literal string "\#" followed by exactly 3 octal
+ digits. Rsync no longer doubles a backslash character in a filename
+ (e.g. it used to output "foo\\bar" when copying "foo\bar") -- now it only
+ escapes a backslash that is followed by a hash-sign and 3 digits (0-9)
+ (e.g. it will output "foo\#134#789" when copying "foo\#789"). See also
+ the --8-bit-output (-8) option, mentioned below.
+
+ Script writers: the local rsync is the one that outputs escaped names,
+ so if you need to support unescaping of filenames for older rsyncs, I'd
+ suggest that you parse the output of "rsync --version" and only use the
+ old unescaping rules for 2.6.5 and 2.6.6.
+
+ BUG FIXES:
+
+ - Fixed a really old bug that caused --checksum (-c) to checksum all the
+ files encountered during the delete scan (ouch).
+
+ - Fixed a potential hang in a remote generator: when the receiver gets a
+ read-error on the socket, it now signals the generator about this so that
+ the generator does not try to send any of the terminating error messages
+ to the client (avoiding a potential hang in some setups).
+
+ - Made hard-links work with symlinks and devices again.
+
+ - If the sender gets an early EOF reading a source file, we propagate this
+ error to the receiver so that it can discard the file and try requesting
+ it again (which is the existing behavior for other kinds of read errors).
+
+ - If a device-file/special-file changes permissions, rsync now updates the
+ permissions without recreating the file.
+
+ - If the user specifies a remote-host for both the source and destination,
+ we now output a syntax error rather than trying to open the destination
+ hostspec as a filename.
+
+ - When --inplace creates a new destination file, rsync now creates it with
+ permissions 0600 instead of 0000 -- this makes restarting possible when
+ the transfer gets interrupted in the middle of sending a new file.
+
+ - Reject the combination of --inplace and --sparse since the sparse-output
+ algorithm doesn't work when overwriting existing data.
+
+ - Fixed the directory name in the error that is output when pop_dir()
+ fails.
+
+ - Really fixed the parsing of a "!" entry in .cvsignore files this time.
+
+ - If the generator gets a stat() error on a file, output it (this used to
+ require at least -vv for the error to be seen).
+
+ - If waitpid() fails or the child rsync didn't exit cleanly, we now handle
+ the exit status properly and generate a better error.
+
+ - Fixed some glitches in the double-verbose output when using --copy-dest,
+ --link-dest, or --compare-dest. Also improved how the verbose output
+ handles hard-links (within the transfer) that had an up-to-date alternate
+ "dest" file, and copied files (via --copy-dest).
+
+ - Fixed the matching of the dont-compress items (e.g. *.gz) against files
+ that have a path component containing a slash.
+
+ - If code reading a filter/exclude file an EINTR error, rsync now clears
+ the error flag on the file handle so it can keep on reading.
+
+ - If --relative is active, the sending side cleans up trailing "/" or "/."
+ suffixes to avoid triggering a bug in older rsync versions. Also, we now
+ reject a ".." dir if it would be sent as a relative dir.
+
+ - If a non-directory is in the way of a directory and rsync is run with
+ --dry-run and --delete, rsync no longer complains about not being able
+ to opendir() the not-yet present directory.
+
+ - When --list-only is used and a non-existent local destination dir was
+ also specified as a destination, rsync no longer generates a warning
+ about being unable to create the missing directory.
+
+ - Fixed some problems with --relative --no-implied-dirs when the
+ destination directory did not yet exist: we can now create a symlink or
+ device when it is the first thing in the missing dir, and --fuzzy no
+ longer complains about being unable to open the missing dir.
+
+ - Fixed a bug where the --copy-links option would not affect implied
+ directories without --copy-unsafe-links (see --relative).
+
+ - Got rid of the need for --force to be used in some circumstances with
+ --delete-after (making it consistent with --delete-before/-during).
+
+ - Rsync now ignores the SIGXFSZ signal, just in case your OS sends this
+ when a file is too large (rsync handles the write error).
+
+ - Fixed a bug in the Proxy-Authorization header's base64-encoded value: it
+ was not properly padded with trailing '=' chars. This only affects a
+ user that need to use a password-authenticated proxy for an outgoing
+ daemon-rsync connection.
+
+ - If we're transferring an empty directory to a new name, rsync no longer
+ forces S_IWUSR if it wasn't already set, nor does it accidentally leave
+ it set.
+
+ - Fixed a bug in the debug output (-vvvvv) that could mention the wrong
+ checksum for the current file offset.
+
+ - Rsync no longer allows a single directory to be copied over a non-
+ directory destination arg.
+
+ ENHANCEMENTS:
+
+ - Added the --append option that makes rsync append data onto files that
+ are longer on the source than the destination (this includes new files).
+
+ - Added the --min-size=SIZE option to exclude small files from the
+ transfer.
+
+ - Added the --compress-level option to allow you to set how aggressive
+ rsync's compression should be (this option implies --compress).
+
+ - Enhanced the parsing of the SIZE value for --min-size and --max-size to
+ allow easy entry of multiples of 1000 (instead of just multiples of 1024)
+ and off-by-one values too (e.g. --max-size=8mb-1).
+
+ - Added the --8-bit-output (-8) option, which tells rsync to avoid escaping
+ high-bit characters that it thinks are unreadable in the current locale.
+
+ - The new option --human-readable (-h) changes the output of --progress,
+ --stats, and the end-of-run summary to be easier to read. If repeated,
+ the units become powers of 1024 instead of powers of 1000. (The old
+ meaning of -h, as a shorthand for --help, still works as long as you
+ just use it on its own, as in "rsync -h".)
+
+ - If lutimes() and/or lchmod() are around, use them to allow the
+ preservation of attributes on symlinks.
+
+ - The --link-dest option now affects symlinks and devices (when possible).
+
+ - Added two config items to the rsyncd.conf parsing: "pre-xfer exec" and
+ "post-xfer exec". These allow a command to be specified on a per-module
+ basis that will be run before and/or after a daemon-mode transfer. (See
+ the man page for a list of the environment variables that are set with
+ information about the transfer.)
+
+ - When using the --relative option, you can now insert a dot dir in
+ the source path to indicate where the replication of the source dirs
+ should start. For example, if you specify a source path of
+ rsync://host/module/foo/bar/./baz/dir with -R, rsync will now only
+ replicate the "baz/dir" part of the source path (note: a trailing
+ dot dir is unaffected unless it also has a trailing slash).
+
+ - Added some new --no-FOO options that make it easier to override unwanted
+ implied or default options. For example, "-a --no-o" (aka "--archive
+ --no-owner") can be used to turn off the preservation of file ownership
+ that is implied by -a.
+
+ - Added the --chmod=MODE option that allows the destination permissions to
+ be changed from the source permissions. E.g. --chmod=g+w,o-rwx
+
+ - Added the "incoming chmod" and "outgoing chmod" daemon options that allow
+ a module to specify what permissions changes should be applied to all
+ files copied to and from the daemon.
+
+ - Allow the --temp-dir option to be specified when starting a daemon, which
+ sets the default temporary directory for incoming files.
+
+ - If --delete is combined with --dirs without --recursive, rsync will now
+ delete in any directory whose content is being synchronized.
+
+ - If --backup is combined with --delete without --backup-dir (and without
+ --delete-excluded), we add a "protect" filter-rule to ensure that files
+ with the backup suffix are not deleted.
+
+ - The file-count stats that are output by --progress were improved to
+ better indicate what the numbers mean. For instance, the output:
+ "(xfer#5, to-check=8383/9999)" indicates that this was the fifth file
+ to be transferred, and we still need to check 8383 more files out of
+ a total of 9999.
+
+ - The include/exclude code now allows a dir/*** directive (with 3 trailing
+ stars) to match both the dir itself as well as all the content below the
+ dir (dir/** would not match the dir).
+
+ - Added the --prune-empty-dirs (-m) option that makes the receiving rsync
+ discard empty chains of directories from the file-list. This makes it
+ easier to selectively copy files from a source hierarchy and end up with
+ just the directories needed to hold the resulting files.
+
+ - If the --itemize-changes (-i) option is repeated, rsync now includes
+ unchanged files in the itemized output (similar to -vv, but without all
+ the other verbose messages that can get in the way). Of course, the
+ client must be version 2.6.7 for this to work, but the remote rsync only
+ needs to be 2.6.7 if you're pushing files.
+
+ - Added the --specials option to tell rsync to copy non-device special
+ files (which rsync now attempts even as a normal user). The --devices
+ option now requests the copying of just devices (character and block).
+ The -D option still requests both (e.g. --devices and --specials), -a
+ still implies -D, and non-root users still get a silent downgrade that
+ omits device copying.
+
+ - Added the --super option to make the receiver always attempt super-user
+ activities. This is useful for systems that allow things such as devices
+ to be created or ownership to be set without being UID 0, and is also
+ useful for someone who wants to ensure that errors will be output if the
+ receiving rsync isn't being run as root.
+
+ - Added the --sockopts option for those few who want to customize the TCP
+ options used to contact a daemon rsync.
+
+ - Added a way for the --temp-dir option to be combined with a partial-dir
+ setting that lets rsync avoid non-atomic updates (for those times when
+ --temp-dir is not being used because space is tight).
+
+ - A new support script, files-to-excludes, will transform a list of files
+ into a set of include/exclude directives that will copy those files.
+
+ - A new option, --executability (-E) can be used to preserve just the
+ execute bit on files, for those times when using the --perms option is
+ not desired.
+
+ - The daemon now logs each connection and also each module-list request
+ that it receives.
+
+ - New log-format options: %M (modtime), %U (uid), %G (gid), and %B
+ (permission bits, e.g. "rwxr-xrwt").
+
+ - The --dry-run option no longer forces the enabling of --verbose.
+
+ - The --remove-sent-files option now does a better job of incrementally
+ removing the sent files on the sending side (older versions tended to
+ clump up all the removals at the end).
+
+ - A daemon now supersedes its minimal SIGCHLD handler with the standard
+ PID-remembering version after forking. This ensures that the generator
+ can get the child-exit status from the receiver.
+
+ - Use of the --bwlimit option no longer interferes with the remote rsync
+ sending error messages about invalid/refused options.
+
+ - Rsync no longer returns a usage error when used with one local source arg
+ and no destination: this now implies the --list-only option, just like
+ the comparable situation with a remote source arg.
+
+ - Added the --copy-dirlinks option, a more limited version of --copy-links.
+
+ - Various documentation improvements, including: a better synopsis, some
+ improved examples, a better discussion of the presence and absence of
+ --perms (including how it interacts with the new --executability and
+ --chmod options), an extended discussion of --temp-dir, an improved
+ discussion of --partial-dir, a better description of rsync's pattern
+ matching characters, an improved --no-implied-dirs section, and the
+ documenting of what the --stats option outputs.
+
+ - Various new and updated diffs in the patches dir, including: acls.diff,
+ xattrs.diff, atimes.diff, detect-renamed.diff, and slp.diff.
+
+ INTERNAL:
+
+ - We now use sigaction() and sigprocmask() if possible, and fall back on
+ signal() if not. Using sigprocmask() ensures that rsync enables all the
+ signals that it needs, just in case it was started in a masked state.
+
+ - Some buffer sizes were expanded a bit, particularly on systems where
+ MAXPATHLEN is overly small (e.g. cygwin).
+
+ - If io_printf() tries to format more data than fits in the buffer, exit
+ with an error instead of transmitting a truncated buffer.
+
+ - If a va_copy macro is defined, lib/snprintf.c will use it when defining
+ the VA_COPY macro.
+
+ - Reduced the amount of stack memory needed for each level of directory
+ recursion by nearly MAXPATHLEN bytes.
+
+ - The wildmatch function was extended to allow an array of strings to be
+ supplied as the string to match. This allows the exclude code to do less
+ string copying.
+
+ - Got rid of the safe_fname() function (and all the myriad calls) and
+ replaced it with a new function in the log.c code that filters all the
+ output going to the terminal.
+
+ - Unified the f_name() and the f_name_to() functions.
+
+ - Improved the hash-table code the sender uses to handle checksums to make
+ it use slightly less memory and run just a little faster.
+
+ DEVELOPER RELATED:
+
+ - The diffs in the patches dir now require "patch -p1 <DIFF" instead of
+ the previous -p0. Also, the version included in the release tar now
+ affect generated files (e.g. configure, rsync.1, proto.h, etc.), so
+ it is no longer necessary to run autoconf and/or yodl unless you're
+ applying a patch that was checked out from CVS.
+
+ - Several diffs in the patches dir now use the proper --enable-FOO
+ configure option instead of --with-FOO to turn on the inclusion of
+ the newly patched feature.
+
+ - There is a new script, "prepare-source" than can be used to update the
+ various generated files (proto.h, configure, etc.) even before configure
+ has created the Makefile (this is mainly useful when patching the source
+ with a patch that doesn't affect generated files).
+
+ - The testsuite now sets HOME so that it won't be affected by a file such
+ as ~/.popt.
+
+\f
+NEWS for rsync 2.6.6 (28 Jul 2005)
+Protocol: 29 (unchanged)
+Changes since 2.6.5:
+
+ SECURITY FIXES:
+
+ - The zlib code was upgraded to version 1.2.3 in order to make it more
+ secure. While the widely-publicized security problem in zlib 1.2.2 did
+ not affect rsync, another security problem surfaced that affects rsync's
+ zlib 1.1.4.
+
+ BUG FIXES:
+
+ - The setting of flist->high in clean_flist() was wrong for an empty list.
+ This could cause flist_find() to crash in certain rare circumstances
+ (e.g. if just the right directory setup was around when --fuzzy was
+ combined with --link-dest).
+
+ - The outputting of hard-linked files when verbosity was > 1 was not right:
+ (1) Without -i it would output the name of each hard-linked file as
+ though it had been changed; it now outputs a "is hard linked" message for
+ the file. (2) With -i it would output all dots for the unchanged
+ attributes of a hard-link; it now changes those dots to spaces, as is
+ done for other totally unchanged items.
+
+ - When backing up a changed symlink or device, get rid of any old backup
+ item so that we don't get an "already exists" error.
+
+ - A couple places that were comparing a local and a remote modification-
+ time were not honoring the --modify-window option.
+
+ - Fixed a bug where the 'p' (permissions) itemized-changes flag might get
+ set too often (if some non-significant mode bits differed).
+
+ - Fixed a really old, minor bug that could cause rsync to warn about being
+ unable to mkdir() a path that ends in "/." because it just created the
+ directory (required --relative, --no-implied-dirs, a source path that
+ ended in either a trailing slash or a trailing "/.", and a non-existing
+ destination dir to tickle the bug in a recent version).
+
+ ENHANCEMENTS:
+
+ - Made the "max verbosity" setting in the rsyncd.conf file settable on a
+ per-module basis (which now matches the documentation).
+
+ - The support/rrsync script has been upgraded to verify the args of options
+ that take args (instead of rejecting any such options). The script was
+ also changed to try to be more secure and to fix a problem in the parsing
+ of a pull operation that has multiple sources.
+
+ - Improved the documentation that explains the difference between a
+ normal daemon transfer and a daemon-over remote-shell transfer.
+
+ - Some of the diffs supplied in the patches dir were fixed and/or
+ improved.
+
+ BUILD CHANGES:
+
+ - Made configure define NOBODY_USER (currently hard-wired to "nobody") and
+ NOBODY_GROUP (set to either "nobody" or "nogroup" depending on what we
+ find in the /etc/group file).
+
+ - Added a test to the test suite, itemized.test, that tests the output of
+ -i (log-format w/%i) and some double-verbose messages.
+
+\f
+NEWS for rsync 2.6.5 (1 Jun 2005)
+Protocol: 29 (unchanged)
+Changes since 2.6.4:
+
+ OUTPUT CHANGES:
+
+ - Non-printable chars in filenames are now output using backslash-
+ escaped characters rather than '?'s. Any non-printable character is
+ output using 3 digits of octal (e.g. "\n" -> "\012"), and a backslash
+ is now output as "\\". Rsync also uses your locale setting, which
+ can make it treat fewer high-bit characters as non-printable.
+
+ - If rsync received an empty file-list when pulling files, it would
+ output a "nothing to do" message and exit with a 0 (success) exit
+ status, even if the remote rsync returned an error (it did not do
+ this under the same conditions when pushing files). This was changed
+ to make the pulling behavior the same as the pushing behavior: we
+ now do the normal end-of-run outputting (depending on options) and
+ exit with the appropriate exit status.
+
+ 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 a bug in the transfer of a single file when -H is specified
+ (rsync would either infinite loop or perhaps crash).
+
+ - Fixed a case where the generator might try (and fail) to tweak the
+ write-permissions of a read-only directory in list-only mode (this
+ only caused an annoying warning message).
+
+ - 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.
+
+ - Fixed the accidental disabling of --backup during the --delete-after
+ processing.
+
+ - Restored the ability to use the --address option in client mode (in
+ addition to its use in daemon mode).
+
+ - 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.
+
+ - When --existing skips a directory with extra verbosity, refer to it
+ as a "directory", not a "file".
+
+ - When transferring a single file to a different-named file, any
+ generator messages that are source-file related no longer refer to
+ the file by the destination filename.
+
+ - Fixed a bug where hard-linking a group of files might fail if the
+ generator hasn't created a needed destination directory yet.
+
+ - Fixed a bug where a hard-linked group of files that is newly-linked
+ to a file in a --link-dest dir doesn't link the files from the rest
+ of the cluster.
+
+ - When deleting files with the --one-file-system (-x) option set, rsync
+ no longer tries to remove files from inside a mount-point on the
+ receiving side. Also, we don't complain about being unable to remove
+ the mount-point dir.
+
+ - Fixed a compatibility problem when using --cvs-ignore (-C) and
+ sending files to an older rsync without using --delete.
+
+ - Make sure that a "- !" or "+ !" include/exclude pattern does not
+ trigger the list-clearing action that is reserved for "!".
+
+ - Avoid a timeout in the generator when the sender/receiver aren't
+ handling the generator's checksum output quickly enough.
+
+ - Fixed the omission of some directories in the delete processing when
+ --relative (-R) was combined with a source path that had a trailing
+ slash.
+
+ - Fixed a case where rsync would erroneously delete some files and then
+ re-transfer them when the options --relative (-R) and --recursive
+ (-r) were both enabled (along with --delete) and a source path had a
+ trailing slash.
+
+ - Make sure that --max-size doesn't affect a device or a symlink.
+
+ - Make sure that a system with a really small MAXPATHLEN does not cause
+ the buffers in readfd_unbuffered() to be too small to receive normal
+ messages. (This mainly affected Cygwin.)
+
+ - If a source pathname ends with a filename of "..", treat it as if
+ "../" had been specified (so that we don't copy files to the parent
+ dir of the destination).
+
+ - If --delete is combined with a file-listing rsync command (i.e. no
+ transfer is happening), avoid outputting a warning that we couldn't
+ delete anything.
+
+ - If --stats is specified with --delete-after, ensure that all the
+ "deleting" messages are output before the statistics.
+
+ - Improved one "if" in the deletion code that was only checking errno
+ for ENOTEMPTY when it should have also been checking for EEXIST (for
+ compatibility with OS variations).
+
+ ENHANCEMENTS:
+
+ - 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 keep-alive code to handle a long silence between the
+ sender and the receiver that can occur when the sender is receiving
+ the checksum data for a large file.
+
+ - 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 (and fatal) 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"
+ instead of a "server" (to distinguish it from the server process 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).
+
+ INTERNAL:
+
+ - Rsync now calls setlocale(LC_CTYPE, ""). This enables isprint() to
+ better discern which filename characters need to be escaped in
+ messages (which should result in fewer escaped characters in some
+ locales).
+
+ - Improved the naming of the log-file open/reopen/close functions.
+
+ - Removed some protocol-compatibility code that was only needed to help
+ someone running a pre-release of 2.6.4.
+
+ BUILD CHANGES:
+
+ - Added configure option "--disable-locale" to disable any use of
+ setlocale() in the binary.
+
+ - Fixed a bug in the SUPPORT{,_HARD}_LINKS #defines which prevented
+ rsync from being built without symlink or hard-link support.
+
+ - Only #define HAVE_REMSH if it is going to be set to 1.
+
+ - Configure now disables the use of mkstemp() under HP-UX (since they
+ refuse to fix its broken handling of large files).
+
+ - 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.
+
+ - Configure no longer mentions the change in the default remote-shell
+ (from rsh to ssh) that occurred for the 2.6.0 release.
+
+ - Some minor enhancements to the test scripts.
+
+ - Added a few new *.diff files to the patches dir, including a patch
+ that enables the optional copying of extended attributes.
+
+\f
NEWS for rsync 2.6.4 (30 March 2005)
Protocol: 29 (changed)
Changes since 2.6.3:
- An OS that has a binary mode for its files (such as cygwin) needed
setmode(fd, O_BINARY) called on the temp-file we opened with
- mkstemp(). (Fix derived from the cygwin's 2.6.3 rsync package.)
+ mkstemp(). (Fix derived from cygwin's 2.6.3 rsync package.)
- Fixed a potential hang when verbosity is high, the client side is
the sender, and the file-list is large.
(since the forked process already has a copy of the exclude list,
there's no need to send them a set of duplicates).
- - When --progress is specified, the output of items that the generator
- is creating (e.g. dirs, symlinks) is now integrated into the progress
- output without overlapping it. (Requires protocol 29.)
+ - The output of the items that are being updated by the generator (dirs,
+ symlinks, devices) is now intermingled in the proper order with the
+ output from the items that the receiver is updating (regular files)
+ when pulling. This misordering was particularly bad when --progress
+ was specified. (Requires protocol 29.)
- When --timeout is specified, lulls that occur in the transfer while
the generator is doing work that does not generate socket traffic
- Handle an operating system that use mkdev() in place of makedev().
- Improved configure to better handle cross-compiling.
+
+\f
NEWS for rsync 2.6.3 (30 Sep 2004)
Protocol: 28 (unchanged)
Changes since 2.6.2:
user chose to combine the output of rsync's stdout and stderr (e.g.
using the "2>&1").
+ - Fixed an option-parsing bug when --files-from got passed to a daemon.
+
ENHANCEMENTS:
- Added the --partial-dir=DIR option that lets you specify where to
- We now reset the "new data has been sent" flag at the start of
each file we send. This makes sure that an interrupted transfer
with the --partial option set doesn't keep a shorter temp file
- than the current basis file when no new data has been transfered
+ than the current basis file when no new data has been transferred
over the wire for that file.
- Fixed a byte-order problem in --batch-mode on big-endian machines.
- Fixed the ability to request an empty backup --suffix when sending
files to an rsync daemon.
+ - Fixed an option-parsing bug when --files-from was sent to a server
+ sender.
+
INTERNAL:
- Most of the I/O is now buffered, which results in a pretty large
\f
Partial Protocol History
RELEASE DATE VER. DATE OF COMMIT* PROTOCOL
+ 22 Apr 2006 2.6.8 29
+ 11 Mar 2006 2.6.7 29
+ 28 Jul 2005 2.6.6 29
01 Jun 2005 2.6.5 29
30 Mar 2005 2.6.4 17 Jan 2005 29
30 Sep 2004 2.6.3 28