Aleksey Tsalolikhin wrote:
I've upgraded from rsync 2.6.9 to 3.0.3 on both ends, but memory usage
is still too high.
Why should rsync 3's memory usage depend on the number of files? Does it
keep files it already knows should not be transferred in memory?
If not, then maybe we should hold
Dear rsync maintainers,
Hi, I have been seeing a problem for awhile in an rsync script I
maintain with how rsync syncs symbolic links between and rsync daemon
running on Linux and an rsync client running on recent Cygwin that I
am wondering is a known issue. Basically rsync always copies
On Tue, 2008-08-12 at 19:11 +0800, Thomas Gutzler wrote:
I've recently noticed that running rsync -m --compare-dest creates
empty directories, even though it should be prevented by the -m flag.
Try rsync -avm --compare-dest=/path/to/dir/ /path/to/dir/ foo
and you get a nice copy of the
On Tue, Aug 12, 2008 at 11:46:11AM -0700, Aleksey Tsalolikhin wrote:
How much memory will rsync use? I didn't specificy any of the
switches that disable incremental recursion.
It depends on your options, and possibly on the maximum number of files
in a directory. I've seen a recursive scan
Thank you, Wayne. My options are:
--server --sender --numeric-ids --perms --owner --group -D --links
--hard-links --times --block-size=2048 --recursive . /
We don't have hard links, AFAIK.
I am archiving 2 months of data, and then I will trying doing another
rsync run, and I'll add the -v
