when trying to open the file. It also no longer constructs names
that start with a double slash (unless the user supplied them).
+ * Path-specifying options to a daemon should now work the same with
+ or without chroot turned on. Previously, such a option (such as
+ --link-dest) would get its absolute path munged into a relative
+ one if chroot was not on, making that setting fairly useless.
+ Rsync now transforms the path into one that is based on the
+ module's base dir when chroot is not enabled.
+
* Fixed compilation problem on Tru64 Unix (having to do with
sockaddr.sa_len and sockaddr.sin_len).
* Fixed a compatibility problem interacting with older rsync
- versions that might send us an empty suffix without telling us
- about the backup-dir.
+ versions that might send us an empty --suffix value without
+ telling us that --backup-dir was specified.
* The "hosts allow" option for a daemon-over-remote-shell
process now has improved support for IPv6 addresses and a fix
for systems that have a length field in their socket structs.
- * Fixed the ability to request an empty backup suffix when
+ * Fixed the ability to request an empty backup --suffix when
sending files to an rsync daemon.
INTERNAL:
* Improved the internal uid/gid code to be more portable and
a little more optimized.
- * Device numbers are now sent as separate major/minor values
- with 32-bit accuracy for each one (protocol 28). Previously
- hard-link device data was sent as a single 64-bit number, and
- copied devices were sent as a single 32-bit number. This will
- make inter-operation of 64-bit binaries more compatible with
- their 32-bit brethren. Note that optimizations in the binary
- protocol often sends the device data using fewer bytes than
- before, even though more precision is now available.
+ * The device numbers sent when using --devices are now sent as
+ separate major/minor values with 32-bit accuracy (protocol 28).
+ Previously, the copied devices were sent as a single 32-bit
+ number. This will make inter-operation of 64-bit binaries more
+ compatible with their 32-bit brethren. Note that optimizations
+ in the binary protocol often sends the device data using fewer
+ bytes than before, even though more precision is now available.
+
+ * Some cleanup of the exclude/include structures and its code
+ made things clearer, simpler, and more efficient.