On Sun, Nov 28, 2021 at 12:53 PM Cristian via rsync
wrote:
$ rsync --copy-unsafe-links -avz --delete tree XXX
In this case, the "tree" directory is a part of the transfer inside the
top-of-transfer dir (the current directory). Thus any symlinks that don't
try to escape the current
To be extra clear (since I was overly terse in my hasty answer), here's
your last example fixed for you:
$ cd ~/dev
$ rsync --copy-unsafe-links -aivz --delete ~/tmp/TST/tree/
~/tmp/XXX/tree/
This is how rsync knows where the safe restriction lies -- at the top of
the transfer (the final
Read the section on --copy-unsafe-symlinks and make the change I
recommended. That's all there is to it. When a dir name is in the
transfer, it is not the top of the transfer tree. It's parent is. This is
pretty standard rsync stuff, where trailing slashes are very important to
rsync.
..wayne..
Hello Wayne
Thank you very much for trying to help,
I have the following three observations:
1) As recommended, I have searched the manual of rsync in order to try
to find your interpretation about what is going on but the only relevant
fact that I was able to find was how rsync defines
On Sun, Nov 28, 2021 at 12:53 PM Cristian via rsync
wrote:
> $ rsync --copy-unsafe-links -avz --delete tree XXX
>
In this case, the "tree" directory is a part of the transfer inside the
top-of-transfer dir (the current directory). Thus any symlinks that don't
try to escape the current directory
Hello all
I have a problem with the --copy-unsafe-links option. My environment is
presented and the end of the message. I have the following directory
structure (I hope the that it will be visible; commands below)
TST/
+-- outside1
| |
| +-- outside1-file.txt
|
+-- outside2-file.txt
|
