X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/f90f71498e85aa0a3ce6f49609bcd70d0ff717c3..6e59b97770496813b1a96f949a2f353adf505dc4:/OLDNEWS diff --git a/OLDNEWS b/OLDNEWS index e8111403..a7c600c3 100644 --- a/OLDNEWS +++ b/OLDNEWS @@ -1,3 +1,555 @@ +NEWS for rsync 2.6.9 (6 Nov 2006) +Protocol: 29 (unchanged) +Changes since 2.6.8: + + BUG FIXES: + + - If rsync is interrupted via a handled signal (such as SIGINT), it will + once again clean-up its temp file from the destination dir. + + - Fixed an overzealous sanitizing bug in the handling of the --link-dest, + --copy-dest, and --compare-dest options to a daemon without chroot: if + the copy's destination dir is deeper than the top of the module's path, + these options now accept a safe number of parent-dir (../) references + (since these options are relative to the destination dir). The old code + incorrectly chopped off all "../" prefixes for these options, no matter + how deep the destination directory was in the module's hierarchy. + + - Fixed a bug where a deferred info/error/log message could get sent + directly to the sender instead of being handled by rwrite() in the + generator. This fixes an "unexpected tag 3" fatal error, and should + also fix a potential problem where a deferred info/error message from + the receiver might bypass the log file and get sent only to the client + process. (These problems could only affect an rsync daemon that was + receiving files.) + + - Fixed a bug when --inplace was combined with a --*-dest option and we + update a file's data using an alternate basis file. The code now + notices that it needs to copy the matching data from the basis file + instead of (wrongly) assuming that it was already present in the file. + + - Fixed a bug where using --dry-run with a --*-dest option with a path + relative to a directory that does not yet exist: the affected option + gets its proper path value so that the output of the dry-run is right. + + - Fixed a bug in the %f logfile escape when receiving files: the + destination path is now included in the output (e.g. you can now tell + when a user specifies a subdir inside a module). + + - If the receiving side fails to create a directory, it will now skip + trying to update everything that is inside that directory. + + - If --link-dest is specified with --checksum but without --times, rsync + will now allow a hard-link to be created to a matching link-dest file + even when the file's modify-time doesn't match the server's file. + + - The daemon now calls more timezone-using functions prior to doing a + chroot. This should help some C libraries to generate proper timestamps + from inside a chrooted daemon (and to not try to access /etc/timezone + over and over again). + + - Fixed a bug in the handling of an absolute --partial-dir=ABS_PATH option: + it now deletes an alternate basis file from the partial-dir that was used + to successfully update a destination file. + + - Fixed a bug in the handling of --delete-excluded when using a per-dir + merge file: the merge file is now honored on the receiving side, and + only its unqualified include/exclude commands are ignored (just as is + done for global include/excludes). + + - Fixed a recent bug where --delete was not working when transferring from + the root (/) of the filesystem with --relative enabled. + + - Fixed a recent bug where an --exclude='*' could affect the root (/) of + the filesystem with --relative enabled. + + - When --inplace creates a file, it is now created with owner read/write + permissions (0600) instead of no permissions at all. This avoids a + problem continuing a transfer that was interrupted (since --inplace + will not update a file that has no write permissions). + + - If either --remove-source-files or --remove-sent-files is enabled and we + are unable to remove the source file, rsync now outputs an error. + + - Fixed a bug in the daemon's "incoming chmod" rule: newly-created + directories no longer get the 'F' (file) rules applied to them. + + - Fixed an infinite loop bug when a filter rule was rejected due to being + overly long. + + - When the server receives a --partial-dir option from the client, it no + longer runs the client-side code that adds an assumed filter rule (since + the client will be sending us the rules in the usual manner, and they + may have chosen to override the auto-added rule). + + ENHANCEMENTS: + + - Added the --log-file=FILE and --log-file-format=FORMAT options. These + can be used to tell any rsync to output what it is doing to a log file. + They work with a client rsync, a non-daemon server rsync (see the man + page for instructions), and also allows the overriding of rsyncd.conf + settings when starting a daemon. + + - The --log-format option was renamed to be --out-format to avoid confusing + it with affecting the log-file output. (The old option remains as an + alias for the new to preserve backward compatibility.) + + - Made "log file" and "syslog facility" settable on a per-module basis in + the daemon's config file. + + - Added the --remove-source-files option as a replacement for the (now + deprecated) --remove-sent-files option. This new option removes all + non-dirs from the source directories, even if the file was already + up-to-date. This fixes a problem where interrupting an rsync that + was using --remove-sent-files and restarting it could leave behind + a file that the earlier rsync synchronized, but didn't get to remove. + (The deprecated --remove-sent-files is still understood for now, and + still behaves in the same way as before.) + + - Added the option --no-motd to suppress the message-of-the-day output + from a daemon when doing a copy. (See the manpage for a caveat.) + + - Added a new environment variable to the pre-/post-xfer exec commands (in + the daemon's config file): RSYNC_PID. This value will be the same in + both the pre- and post-xfer commands, so it can be used as a unique ID + if the pre-xfer command wants to cache some arg/request info for the + post-xfer command. + + INTERNAL: + + - Did a code audit using IBM's code-checker program and made several + changes, including: replacing most of the strcpy() and sprintf() + calls with strlcpy(), snprintf(), and memcpy(), adding a 0-value to + an enum that had been intermingling a literal 0 with the defined enum + values, silencing some uninitialized memory checks, marking some + functions with a "noreturn" attribute, and changing an "if" that + could never succeed on some platforms into a pre-processor directive + that conditionally compiles the code. + + - Fixed a potential bug in f_name_cmp() when both the args are a + top-level "." dir (which doesn't happen in normal operations). + + - Changed exit_cleanup() so that it can never return instead of exit. + The old code might return if it found the exit_cleanup() function + was being called recursively. The new code is segmented so that + any recursive calls move on to the next step of the exit-processing. + + - The macro WIFEXITED(stat) will now be defined if the OS didn't already + define it. + + DEVELOPER RELATED: + + - The acls.diff and xattrs.diff patches have received a bunch of work to + make them much closer to being acceptable in the main distribution. + The xattrs patch also has some preliminary Mac OS X and FreeBSD + compatibility code that various system types to exchange extended + file-attributes. + + - A new diff in the patches dir, fake-root.diff, allows rsync to + maintain a backup hierarchy with full owner, group, and device info + without actually running as root. It does this using a special + extended attribute, so it depends on xattrs.diff (which depends on + acls.diff). + + - The rsync.yo and rsyncd.conf.yo files have been updated to work + better with the latest yodl 2.x releases. + + - Updated config.guess and config.sub to their 2006-07-02 versions. + + - Updated various files to include the latest FSF address and to have + consistent opening comments. + + +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). + + +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 the code reading a filter/exclude file gets 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 1 was not right: - 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); 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). + (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. @@ -294,7 +846,7 @@ 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. @@ -359,9 +911,11 @@ Changes since 2.6.3: (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 @@ -768,6 +1322,8 @@ 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 @@ -981,7 +1537,7 @@ Changes since 2.6.0: - 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. @@ -1034,6 +1590,9 @@ Changes since 2.6.0: - 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 @@ -1293,7 +1852,7 @@ Changes since 2.5.5: * The --suffix option can now be used with --backup-dir. (Michael Zimmerman) - * Combining "::" syntax with the -rsh/-e option now uses the + * Combining "::" syntax with the --rsh/-e option now uses the specified remote-shell as a transport to talk to a (newly-spawned) server-daemon. This allows someone to use daemon features, such as modules, over a secure protocol, such as ssh. (JD Paul) @@ -1685,6 +2244,11 @@ Changes since 2.4.6: Partial Protocol History RELEASE DATE VER. DATE OF COMMIT* PROTOCOL + ?? ??? 2008 3.0.0 11 Nov 2006 30 + 06 Nov 2006 2.6.9 29 + 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