Hi Horst,
thanks for the hint, I made this error because I assembled the
block from command history (without testing it again...), but I tested
now that
X=`mktemp -d`
echo "abc" > $X/1
echo "abc1" > $X/2
Y=`mktemp -d`
echo "abc" > $Y/1
echo "abc2" > $Y/2
rsync --dry-run --info=COPY -r -c $X $Y
g
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 Mon, Jun 16, 2014 at 5:29 AM, Karl-Philipp Richter
wrote:
>
> X=`mktemp`
> echo "abc" > $X/1
> echo "abc1" > $X/2
> Y=`mktemp`
> echo "abc" > $Y/1
> echo "abc2" > $Y/2
>
I'll assume you meant to use -d on your mktemp commands (as another
responder *almost* pointed out).
> * `rsync --dry
Hi,
Karl-Philipp Richter (Mo 16 Jun 2014 14:29:04 CEST):
> Hi together,
> after I read "very often" without even a tiny bit of a contradiction, I
> start to have the feeling I have a basic misunderstanding of rsync.
>
> Assume one want to get a list of files which would have been transfered
> by
Hi together,
after I read "very often" without even a tiny bit of a contradiction, I
start to have the feeling I have a basic misunderstanding of rsync.
Assume one want to get a list of files which would have been transfered
by rsync if rsync was requested to sync directories X and Y and one does