oldnews

Rsync 3.0.5 source code

    - Fixed a couple minor bugs in the included popt library (ones which I
      sent to the official popt project for inclusion in the 1.14 release).

    - Fixed a stat() call that should have been do_stat() so that the proper
      normal/64-bit stat() function gets called.  (Was in an area that should
      not have caused problems, though.)

    - Changed the file-glob code to do a directory scan without using the
      "glob" and "glob.h".  This lets us do the globbing with less memory
      churn, and also avoid adding daemon-excluded items to the returned
      args.

  DEVELOPER RELATED:

    - The configure script tries to get the user's compiler to not warn about
      unused function parameters if the build is not including one or more of
      the ACL/xattrs/iconv features.

    - The configure script now has better checks for figuring out if the
      included popt code should be used or not.

    - Fixed two testsuite glitches: avoid a failure if someone's "cd" command
      outputs the current directory when cd-ing to a relative path, and made
      the itemized test query how rsync was built to determine if it should
      expect hard-linked symlinks or not.

    - Updated the testsuite to verify that various bug fixes remain fixed.

    - The RPM spec file was updated to have: (1) comments for how to use the
      rsync-patch tar file, and (2) an /etc/xinetd.d/rsync file.

    - Updated the build scripts to work with a revised FTP directory
      structure.


NEWS for rsync 3.0.0 (1 Mar 2008)
Protocol: 30 (changed)
Changes since 2.6.9:

  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 individuals 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.)
      Also, exclude rules no longer have a partial effect on implied dirs.

    - Requesting a remote file-listing 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.

    - In --dry-run mode, the last line of the verbose summary text is output
      with a "(DRY RUN)" suffix to help remind you that no updates were made.
      Similarly, --only-write-batch outputs "(BATCH ONLY)".

    - A writable rsync daemon with "use chroot" disabled now defaults to a
      symlink-munging behavior designed to make symlinks safer while also
      allowing absolute symlinks to be stored and retrieved.  This also has
      the effect of making symlinks unusable while they're in the daemon's
      hierarchy.  See the daemon's "munge symlinks" parameter for details.

    - Starting up an extra copy of an rsync daemon will not clobber the pidfile
      for the running daemon -- if the pidfile exists, the new daemon will exit
      with an error.  This means that your wrapper script that starts the rsync
      daemon should be made to handle lock-breaking (if you want any automatic
      breaking of locks to be done).

  BUG FIXES:

    - A daemon with "use chroot = no" and excluded items listed in the daemon
      config file now properly checks an absolute-path arg specified for these
      options:  --compare-dest, --link-dest, --copy-dest, --partial-dir,
      --backup-dir, --temp-dir, and --files-from.

    - A daemon can now be told to disable all user- and group-name translation
      on a per-module basis.  This avoids a potential problem with a writable
      daemon module that has "use chroot" enabled -- if precautions weren't
      taken, a user could try to add a missing library and get rsync to use
      it.  This makes rsync safer by default, and more configurable when id-
      translation is not desired.  See the daemon's "numeric ids" parameter
      for full details.

    - A chroot daemon can now indicate which part of its path should affect the
      chroot call, and which part should become an inside-chroot path for the
      module.  This allows you to have outside-the-transfer paths (such as for
      libraries) even when you enable chroot protection.  The idiom used in the
      rsyncd.conf file is:  path = /chroot/dirs/./dirs/inside

    - If a file's data arrived successfully on the receiving side but the
      rename of the temporary file to the destination file failed AND the
      --remove-source-files (or the deprecated --remove-sent-files) option
      was specified, rsync no longer erroneously removes the associated
      source file.

    - Fixed the output of -ii when combined with one of the --*-dest options:
      it now itemizes all the items, not just the changed ones.

    - Made the output of all file types consistent when using a --*-dest
      option.  Prior versions would output too many creation events for
      matching items.

    - The code that waits for a child pid now handles being interrupted by a
      signal.  This fixes a problem with the pre-xfer exec function not being
      able to get the exit status from the script.

    - A negated filter rule (i.e. with a '!' modifier) no longer loses the
      negation when sending the filter rules to the remote rsync.

    - Fixed a problem with the --out-format (aka --log-format) option %f:  it
      no longer outputs superfluous directory info for a non-daemon rsync.

    - Fixed a problem with -vv (double --verbose) and --stats when "pushing"
      files (which includes local copies).  Version 2.6.9 would complete the
      copy, but exit with an error when the receiver output its memory stats.

    - If --password-file is used on a non-daemon transfer, rsync now complains
      and exits.  This should help users figure out that they can't use this
      option to control a remote shell's password prompt.

    - Make sure that directory permissions of a newly-created destination
      directory are handled right when --perms is left off.

    - The itemized output of a newly-created destination directory is now
      output as a creation event, not a change event.

    - Improved --hard-link so that more corner cases are handled correctly
      when combined with options such as --link-dest and/or --ignore-existing.

    - The --append option no longer updates a file that has the same size.

    - Fixed a bug when combining --backup and --backup-dir with --inplace:
      any missing backup directories are now created.

    - Fixed a bug when using --backup and --inplace with --whole-file or
      --read-batch: backup files are actually created now.

    - 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).

    - Ensure that a temporary file always has owner-write permission while we
      are writing to it.  This avoids problems with some network filesystems
      when transfering read-only files.

    - Any errors output about password-file reading no longer cause an error at
      the end of the run about a partial transfer.

    - The --read-batch option for protocol 30 now ensures that several more
      options are set correctly for the current batch file:  --iconv, --acls,
      --xattrs, --inplace, --append, and --append-verify.

    - Using --only-write-batch to a daemon receiver now works properly (older
      versions would update some files while writing the batch).

    - Avoid outputting a "file has vanished" message when the file is a broken
      symlink and --copy-unsafe-links or --copy-dirlinks is used (the code
      already handled this for --copy-links).

    - Fixed the combination of --only-write-batch and --dry-run.

    - Fixed rsync's ability to remove files that are not writable by the file's
      owner when rsync is running as the same user.

    - When transferring large files, the sender's hashtable of checksums is
      kept at a more reasonable state of fullness (no more than 80% full) so
      that the scanning of the hashtable will not bog down as the number of
      blocks increases.

  ENHANCEMENTS:

    - A new incremental-recursion algorithm is now used when rsync is talking
      to another 3.x version.  This starts the transfer going more quickly
      (before all the files have been found), and requires much less memory.
      See the --recursive option in the manpage for some restrictions.

    - 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
      3.x rsync.  This is a faster scan than using --delete-before (which is
      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 an empty one
      (e.g. empty:  :file1  or  ::module/file2).  For example, this means that
      local use of brace expansion now works:  rsync -av host:dir/{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.

    - Added the --acls (-A) option to preserve Access Control Lists.  This is
      an improved version of the prior patch that was available, and it even
      supports OS X ACLs.  If you need to have backward compatibility with old,
      ACL-patched versions of rsync, apply the acls.diff file from the patches
      dir.

    - Added the --xattrs (-X) option to preserve extended attributes.  This is
      an improved version of the prior patch that was available, and it even
      supports OS X xattrs (which includes their resource fork data).  If you
      need to have backward compatibility with old, xattr-patched versions of
      rsync, apply the xattrs.diff file from the patches dir.

    - Added the --fake-super option that allows a non-super user to preserve
      all attributes of a file by using a special extended-attribute idiom.
      It even supports the storing of foreign ACL data on your backup server.
      There is also an analogous "fake super" parameter for an rsync daemon.

    - Added the --iconv option, which allows rsync to convert filenames from
      one character-set to another during the transfer.  The default is to
      make this feature available as long as your system has iconv_open().
      If compilation fails, specify --disable-iconv to configure, and then
      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
      explanation of the --iconv option's settings.

    - A new daemon config parameter, "charset", lets you control the character-
      set that is used during an --iconv transfer to/from a daemon module.  You
      can also set your daemon to refuse "no-iconv" if you want to force the
      client to use an --iconv transfer (requiring an rsync 3.x client).

    - Added the --skip-compress=LIST option to override the default list of
      file suffixes that will not be compressed when using --compress (-z).

    - The daemon's default for "dont compress" was extended to include:
	  *.7z *.mp[34] *.mov *.avi *.ogg *.jpg *.jpeg
      The name-matching routine was also optimized to run more quickly.

    - The --max-delete option now outputs a warning if it skipped any file
      deletions, including a count of how many deletions were skipped.  (Older
      versions just silently stopped deleting things.)

    - You may specify --max-delete=0 to a 3.0.0 client to request that it warn
      about extraneous files without deleting anything.  If you're not sure
      what version the client is, you can use the less-obvious --max-delete=-1,
      as both old and new versions will treat that as the same request (though
      older versions don't warn).

    - 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 (rather than adding more
      data), and limits the in-memory storage of the device+inode information
      to just the sending side for the new protocol 30, or to the receiving
      side when speaking an older protocol (note that older rsync versions kept
      the device+inode information on both sides).

    - The filter rules now support a perishable ("p") modifier that marks rules
      that should not have an effect in a directory that is being deleted.  e.g.
      -f '-p .svn/' would only affect "live" .svn directories.

    - Rsync checks all the alternate-destination args for validity (e.g.
      --link-dest).  This lets the user know when they specified a directory
      that does not exist.

    - If we get an ENOSYS error setting the time on a symlink, we don't
      complain about it anymore (for those systems that even support the
      setting of the modify-time on a symlink).

    - Protocol 30 now uses MD5 checksums instead of MD4.

    - Changed the --append option to not checksum the existing data in the
      destination file, which speeds up file appending.

    - Added the --append-verify option, which works like the older --append