On Mon, Jun 16, 2014 at 10:51 AM, Chris Thompson wrote:
> but rather than hardlinking the first symlink it hardlinks its
> *target* (or fails if the target doesn't exist [yet]).
>
Yeah, that's what configure is testing for -- that link() doesn't work
right with symlinks (it affects the referent
This begins to feel like sinking further and further into the tar pit ...
Forcibly setting "#define CAN_HARDLINK_SYMLINK 1" in config.h after
configure and then make'ing gives an rsync that is only slightly better
behaved. It doesn't hang any longer (in any combination so far tried),
but rather t
On Sun, Jun 15, 2014 at 3:08 PM, Chris Thompson wrote:
> But this suggests something wrong with the configure script, as Solaris
> 10_x86 is perfectly capable of hardlinking symlinks.
>
I'd imagine that your configure run was done on a filesystem that didn't
support hardlinked symlinks, since th
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 fine
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 fine for quite a while.
Apparently the we-
