Am 14.11.19 um 16:25 schrieb Pierre Bernhardt:
> Is this for linke backup reason if the source dir is different
> from the link-dest dir because of different hosts like
>
> rsync -av --dest-link=../a a/ backuphost:b/
>
> where on backuphost a is an older copy and b is the new
> target?
Yea, that'
Am 14.11.19 um 15:02 schrieb Paul Slootman via rsync:
> On Thu 14 Nov 2019, Pierre Bernhardt via rsync wrote:
> So it's looking for b/a as the link-dest directory.
>
> Use a full pathname for --link-dest to remove all uncertainty.
> E.g.:
>
> rsync -av --link-dest=$(pwd)/a a/ b/
>
> In this
On Thu 14 Nov 2019, Pierre Bernhardt via rsync wrote:
> Am 14.11.19 um 10:54 schrieb Paul Slootman via rsync:
> > You need to specify the source directory as the link-dest directory.
>
> Hi, I tried it also because it's an old question which has never worked
> for me. Instead it creates copies and
Am 14.11.19 um 10:54 schrieb Paul Slootman via rsync:
> You need to specify the source directory as the link-dest directory.
Hi, I tried it also because it's an old question which has never worked
for me. Instead it creates copies and not hard links:
pierre@in94:~/tmp$ ls -li a b
a:
insgesamt 8
On Thu 14 Nov 2019, L A Walsh via rsync wrote:
> Have a directory with a bunch rpms in it, mostly x86_64.
>
> Have another directory with a bunch, mostly 'noarch'.
>
> Some of the noarch files are already in the x86_64 dir
> and don't want to overwrite them. They are on the same
> physical disk
Have a directory with a bunch rpms in it, mostly x86_64.
Have another directory with a bunch, mostly 'noarch'.
Some of the noarch files are already in the x86_64 dir
and don't want to overwrite them. They are on the same
physical disk, so really, just want the new 'noarch' files
hardlinked into
