An open source utility that provides fast incremental file transfer. It also has useful features for backup and restore operations among many other use cases.
I am on rsync version 3.2.7 protocol version 31, currently on an Arch Linux.
The following I would expect to copy the contents of 'a' to 'c', based on my understanding of the the advice in man rsync for using --fake-super locally:
mkdir a b c
touch a/hello
rsync -M--fake-super -a a/ b/
rsync --super -M--fake-super -a b/ c/
Instead I see 'c' unchanged, and a garbage directory created with the expected contents in the local directory:
Note, this always writes the garbage directory into the current directory, even if it is on a different filesystem than the source, destination, and (/tmp or -T).
A workaround is to use rsync to/from localhost: instead.
(Also posted to mailing list as https://lists.samba.org/archive/rsync/2023-July/033045.html)
I am on rsync version 3.2.7 protocol version 31, currently on an Arch Linux.
The following I would expect to copy the contents of 'a' to 'c', based on my understanding of the the advice in
man rsync
for using --fake-super locally:Instead I see 'c' unchanged, and a garbage directory created with the expected contents in the local directory:
Note, this always writes the garbage directory into the current directory, even if it is on a different filesystem than the source, destination, and (/tmp or -T).
A workaround is to use rsync to/from localhost: instead.