ll
the #defines's) it gives exit code 0.
Some historical research indicates that something changed here between
rsync 3.0.5 and 3.0.6. I found some old build directories on one
Solaris 10_x86 system (not all made by me, so it doesn't seem to be
a personal idioscyncracy). Running configure
On Jun 14 2014, Wayne Davison wrote:
On Fri, Jun 13, 2014 at 12:29 PM, Chris Thompson wrote:
When copying these with -H, rsync gets more than a little confused:
Your rsync must be configured without CAN_HARDLINK_SYMLINK being defined
(see config.h), as the normal code has been working
target is local or remote.
I have variants where -R is being used as well as -H.
Before trying to officially report this, I thought I would ask on this
mailing list whether anyone can reproduce the problem.
--
Chris Thompson
Email: c...@cam.ac.uk
--
Please use reply-all for most replies to av
