On Sun, Jan 04, 2004 at 04:07:10PM -0800, jw schultz wrote:
> Wayne has a patch in CVS to prevent the [copy on write].
FYI, I have noticed that my improvements do not affect the case where
file permissions are not being preserved -- that code path still sets a
bunch of mode values based on local f
RE: Change of email address.
Happy New Year 2004!
Please be advised that my NEW email address is [EMAIL PROTECTED]
The resume is still at:
http://zar.ukcontract.net
Just email me if you need a Word or PDF copy at [EMAIL PROTECTED]
Thank you:
ZAR
--
To unsubscribe or chan
On Sun, Jan 04, 2004 at 05:30:03AM -0800, jw schultz wrote:
> On Sun, Jan 04, 2004 at 06:35:03AM -0600, John Van Essen wrote:
> > I've modified hlink.c to use a list of file struct pointers instead of
> > copies of the actual file structs themselves, so that will save memory.
> > I'll submit that p
Minor corrections...
On Sun, Jan 04, 2004 at 06:35:03AM -0600, John Van Essen wrote:
> Lester,
>
> You articulated your situation clear enough for me. Thanks.
>
> I'll address your issue about when rsync is running locally for /vol/N
> to /vol/N_mirror syncing, it exhausts all of the RAM and sw
On Sun, Jan 04, 2004 at 09:45:59AM -0800, Wayne Davison wrote:
> FYI, it doesn't appear that you need to change the hlink_compare()
> function to take "struct file_struct **" args instead of just "... *".
Oops, I didn't notice the qsort() call. Sorry -- ignore this.
..wayne..
--
To unsubscribe
On Sun, Jan 04, 2004 at 06:35:03AM -0600, John Van Essen wrote:
> The sender, receiver, and generator each have a full copy of the file
> list (each file's entry uses 100 bytes on average).
On systems with copy-on-write forking, the file list memory is shared
between the receiver and the generator
On Sun, Jan 04, 2004 at 05:30:03AM -0800, jw schultz wrote:
> I've just done the same. It reduces the memory requirements
> of the hlink list to 1/18th.
FYI, it doesn't appear that you need to change the hlink_compare()
function to take "struct file_struct **" args instead of just "... *".
I just
On Sun, Jan 04, 2004 at 06:35:03AM -0600, John Van Essen wrote:
> Lester,
>
> You articulated your situation clear enough for me. Thanks.
>
> I'll address your issue about when rsync is running locally for /vol/N
> to /vol/N_mirror syncing, it exhausts all of the RAM and swap.
>
> If you haven'
Lester,
You articulated your situation clear enough for me. Thanks.
I'll address your issue about when rsync is running locally for /vol/N
to /vol/N_mirror syncing, it exhausts all of the RAM and swap.
If you haven't read jw schultz's "How Rsync Works" page, here the link:
http://www.pegasys
On Fri, Jan 02, 2004 at 10:52:01AM -0600, Max Kipness wrote:
> By adding the --size-only option, this behavior has changed and only
> changes in file size are being transferred. Is there any negative
> effect to using this option?
If there can be a change in a file but the file stays the same size
On Sat, Jan 03, 2004 at 01:00:09PM -0800, Wayne Davison wrote:
| On Sat, Jan 03, 2004 at 02:11:04AM -0600, Phil Howard wrote:
| > After doing a fresh extraction of the source for 2.6.0, I execute
| > ./configure and it enters a loop with no output before or during.
|
| What shell are you using?
11 matches
Mail list logo
