Why does one of there work and the other doesn't

[tim.conway at philips.com]

100bytes/file of file information for every file, whether it is to be 
transferred or not.  YMMV

Tim Conway
tim.conway at philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn, 
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), 
".\n" '
"There are some who call me.... Tim?"




Randy Kramer <rhkramer at fast.net>
Sent by: rsync-admin at lists.samba.org
11/30/2001 10:01 AM

 
        To:     Martin Pool <mbp at samba.org>
        cc:     Ian Kettleborough <ian at idk.com>
rsync at samba.org
(bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        Re: Why does one of there work and the other doesn't
        Classification: 



Martin Pool wrote:
> Ian Kettleborough <ian at idk.com> wrote:
> > 1. How much memory does each file to be copied need. Obvisiouly I have 
too many
> > files.
> 
> Hard to say exactly.  On the order of a hundred bytes per file.

I may have misunderstood the question, but maybe we should point out
that, on the receiving end, each file needs at least an amount of *disk
space* equal in size to the file as a new file is constructed before the
old file is deleted. 

I am not sure which end the 100 bytes per file applies to, and I guess
that is the RAM memory footprint?.  Does rsync need 100 bytes for each
file that might be transferred during a session (all files in the
specified directory(ies)), or does it need only 100 bytes as it does one
file at a time?

Trying to learn, also,
Randy Kramer