On Mon, Dec 03, 2001 at 09:55:53AM -0700, [EMAIL PROTECTED] wrote:
| rsync already has a memory-hogging issue. Imagine having it search your
| entire directory tree, checksumming all files, storing and sending them
| all, comparing both lists looking for matching date/time/checksums to
| gues
1 09:04 AM
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: Re: Why does one of there work and the other doesn't
Classification:
On Mon, Dec 03, 2001 at 12:09:16AM +1100, Martin Pool wrote:
| On 30 Nov 2001, Randy Kramer <[E
On Sun, Dec 02, 2001 at 09:31:25PM -0500, Mark Eichin wrote:
| > Perhaps a trailing "/" instead of training "/." is supposed to work. I do
| > not remember why I didn't start using it, but I am sure I would have tried
|
| Quite possibly because you've been bitten by class cp/rcp; cp is not
| id
On Mon, Dec 03, 2001 at 12:09:16AM +1100, Martin Pool wrote:
| On 30 Nov 2001, Randy Kramer <[EMAIL PROTECTED]> wrote:
|
| > 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 tr
> Perhaps a trailing "/" instead of training "/." is supposed to work. I do
> not remember why I didn't start using it, but I am sure I would have tried
Quite possibly because you've been bitten by class cp/rcp; cp is not
idempotent, in that if you "cp -r foo bar" where foo is a dir and bar
doe
On 30 Nov 2001, Randy Kramer <[EMAIL PROTECTED]> wrote:
> 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))
On Fri, Nov 30, 2001 at 07:42:17AM -0700, [EMAIL PROTECTED] wrote:
| from "man rsync":
| a trailing slash on the source changes this behavior to
| transfer all files from the directory src/bar on the machine
| foo into the /data/tmp/. A trailing / on a source name
|
;[EMAIL PROTECTED]>
cc: Ian Kettleborough <[EMAIL PROTECTED]>
[EMAIL PROTECTED]
(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 <[EMAIL PRO
From: Randy Kramer [mailto:[EMAIL PROTECTED]]
> 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
Martin Pool wrote:
> Ian Kettleborough <[EMAIL PROTECTED]> 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 ou
from "man rsync":
a trailing slash on the source changes this behavior to
transfer all files from the directory src/bar on the machine
foo into the /data/tmp/. A trailing / on a source name
means "copy the contents of this directory". Without a
trailing sl
On 29 Nov 2001, Ian Kettleborough <[EMAIL PROTECTED]> 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.
> 2. Why does this command work:
>
> rsync -ax /usr/xx /backup/usr/
>
>
12 matches
Mail list logo
