On Mar 1, 2012, at 21:52, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Is it actually not doing anything? It should only list files that it
> is actually doing something with unless you use more than one -v. Try
> adding --itemize-changes to find out (-v is fairly us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it actually not doing anything? It should only list files that it
is actually doing something with unless you use more than one -v. Try
adding --itemize-changes to find out (-v is fairly useless without it
anyway).
Also, don't use -z unless you a
Thanks to all for jumping in on this one. I've used rsync in a kind of offhand
manner for years, only now was it necessary to "get serious" with it
So then, using -a **includes** -r? Goodness me, I was using -ra so who knows
what gnarliness I was actually causing!!
If I can briefly say what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, -a includes -r and a bunch of other things.
- --no-i-r disables the incremental recursion and forces rsync to hold
the entire tree in memory in addition to fully scanning the tree on
both ends before copying anything.
On 03/01/12 14:39, Elliot W
On Mar 1, 2012, at 11:34 AM, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Without -r rsync will ignore all directories even if the path you
> specified is a directory. That is what recursive means.
>
> If you are having memory usage issues make sure you are running rs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Without -r rsync will ignore all directories even if the path you
specified is a directory. That is what recursive means.
If you are having memory usage issues make sure you are running rsync
version 3 on both ends and check that you aren't using any
Without the -r switch, I believe that rsync will ignore directory trees. Very
often, I think rsync is run with -a, which includes -r, so it's easy to miss
this fact.
If you want to reduce memory/processor demand, I think that
-r --no-i-r
may help.
On Mar 1, 2012, at 6:29 AM, Colin Raven wrot
