The company I work for uses rsync for backups from client computers,
the memory usage is a problem for a lot of them since they're already
busy doing other important things (databases, web serving, etc).
From the FAQ:
out of memory
The usual reason for "out of memory" when running rsync is t
[...]
> 1) Free: break your rsync's into several executions rather than one huge
> one. Do several sub-directory trees, each separately. If your data
> files are not organized in such a way that they can easily be divided
> into a reasonable number of sub-directory trees, consider re-orga
On Wed, Jul 06, 2005 at 01:13:23AM -0500, Matthew S. Hallacy wrote:
> Unfortunately there's no indication of who needs a spare week of
> coding time, or how much a week would cost.
That's a really old comment, so I'm not sure if it was written by Martin
Pool or Dave Dykstra or someone else. I'm
On Wed 06 Jul 2005, David Favro wrote:
>
> 1) Free: break your rsync's into several executions rather than one huge
> one. Do several sub-directory trees, each separately. If your data
[...]
> 2) Cheap: buy more swap space. These days random-access magnetic
[...]
> 4) Expensive: buy more solid-
Hi, Matthew --
Regarding your message of 05-Jul-2005 concerning rsync memory usage
(sorry that I am not directly replying to it; I am not as yet subscribed
to the list and my mailer doesn't allow me to hard-code an In-Reply-To
or References header):
While I applaud anyone who wants to encourage o
Hello,
The company I work for uses rsync for backups from client computers,
the memory usage is a problem for a lot of them since they're already
busy doing other important things (databases, web serving, etc).
>From the FAQ:
---
out of memory
The usual reason for "out of memory" when running
