On 12 Jun 2003, jw schultz [EMAIL PROTECTED] wrote:
Mind you, that means making the server lightweight with the
client doing all the logic and a nearly stateless connection.
Much like my earlier post on this thread posited.
I was wondering today if that would make it easier to gain confidence
Recently hit a problem
rsync 2.5.6 protocol 26 from cvs a few months ago
(why does current cvs still say 2.5.6 yet protocol 27?)
built on sco open server 5.0.6
doing some nightly backups of some huge trees.
some of the files appraoch 2 gigs
one file in particular did reach 2 gigs on the live
jw schultz [EMAIL PROTECTED] wrote:
On Mon, Jun 09, 2003 at 01:56:34PM -0400, Hardy Merrill wrote:
AFAICT, back in the vicinity of January 2002, a patch
(call this patch 'A') was developed to close an 'rsync
remote hole' - the patch switched variables in
'sum_struct' to size_t. According
Using an rsync (V2.5.6, Tru64 Unix 5.1A) command of the form:
rsync -avz --delete /some/dir remhost:/some/other/dir
where /some/dir has about 460,000 files in it, I get:
building file list ... done
ERROR: out of memory in make_file
rsync error: error allocating core memory buffers (code
On Fri, Jun 13, 2003 at 12:39:06PM -0400, Steve Thompson wrote:
Using an rsync (V2.5.6, Tru64 Unix 5.1A) command of the form:
rsync -avz --delete /some/dir remhost:/some/other/dir
where /some/dir has about 460,000 files in it, I get:
building file list ... done
ERROR: out of
