Re: [freenet-support] routing table

2004-02-16 Thread Jim Dixon
[EMAIL PROTECTED] Mon Feb 16 14:05:35 2004 wrote in an attachment: > > It is noticeable that Freenet uses a ridiculous amount of RAM. If I run > > top on a node that connects to only one other node, and sporadically at > > that, I see that it is using 79 MB of memory. The number doesn't appear >

Re: [freenet-support] routing table

2004-02-16 Thread Toad
On Sun, Feb 15, 2004 at 10:37:16PM +, Jim Dixon wrote: > On Sun, 15 Feb 2004, Niklas Bergh wrote: > > > > It is noticeable that Freenet uses a ridiculous amount of RAM. If I run > > > top on a node that connects to only one other node, and sporadically at > > > that, I see that it is using 79

Re: [freenet-support] routing table

2004-02-16 Thread Toad
On Sun, Feb 15, 2004 at 09:00:36PM +, Jim Dixon wrote: > On Fri, 13 Feb 2004, Paul Derbyshire wrote: > > > > Freeing up RAM is not related to routing table at all. Unfortunately, > > > Freenet code contains a bug (a so called "memory leak") which takes > > > memory from your OS, but then "forg

Re: [freenet-support] routing table

2004-02-15 Thread Jim Dixon
On Sun, 15 Feb 2004, Niklas Bergh wrote: > > It is noticeable that Freenet uses a ridiculous amount of RAM. If I run > > top on a node that connects to only one other node, and sporadically at > > that, I see that it is using 79 MB of memory. The number doesn't appear > > to grow -- there is no

Re: [freenet-support] routing table

2004-02-15 Thread Niklas Bergh
> It is noticeable that Freenet uses a ridiculous amount of RAM. If I run > top on a node that connects to only one other node, and sporadically at > that, I see that it is using 79 MB of memory. The number doesn't appear > to grow -- there is no evidence of a memory leak -- but it starts out and

Re: [freenet-support] routing table

2004-02-15 Thread Jim Dixon
On Fri, 13 Feb 2004, Paul Derbyshire wrote: > > Freeing up RAM is not related to routing table at all. Unfortunately, > > Freenet code contains a bug (a so called "memory leak") which takes > > memory from your OS, but then "forgets" about it, not using it and > > not returning it - so the amount

Re: [freenet-support] routing table

2004-02-14 Thread Toad
On Sat, Feb 14, 2004 at 09:34:06AM +0100, Niklas Bergh wrote: > > Is it a VM bug or is it just creating > > objects it theoretically could reach (thus they don't get GC'd), but > > ignores forever? > > The second it what is defined as a 'memory leak' in GC'd environments. Or a "space leak". >

Re: [freenet-support] routing table

2004-02-14 Thread Niklas Bergh
> Is it a VM bug or is it just creating > objects it theoretically could reach (thus they don't get GC'd), but > ignores forever? The second it what is defined as a 'memory leak' in GC'd environments. /N ___ Support mailing list [EMAIL PROTECTED] http

Re: [freenet-support] routing table

2004-02-13 Thread Paul Derbyshire
On 13 Feb 2004 at 15:29, Victor Denisov wrote: > Freeing up RAM is not related to routing table at all. Unfortunately, > Freenet code contains a bug (a so called "memory leak") which takes > memory from your OS, but then "forgets" about it, not using it and > not returning it - so the amount of

Re: [freenet-support] routing table

2004-02-13 Thread Victor Denisov
  Regards, Victor Denisov,CEO, Jera Systems, Moscow, Russia - Original Message - From: Robert Greenage To: [EMAIL PROTECTED] Sent: Friday, February 13, 2004 4:15 PM Subject: RE: [freenet-support] routing table I want to free up RAM memory. I only have 192 mbs. I

RE: [freenet-support] routing table

2004-02-13 Thread Robert Greenage
5:09:02 AM Subject: RE: [freenet-support] routing table The routingtable files are the rtnodes_* and rtprops_* files in your choosen freenet install folder. However.. these files occupies only a few kilobytes of your harddrive.   Is it HD space or RAM memory you want to free up?   /N -Ori

RE: [freenet-support] routing table

2004-02-13 Thread Niklas Bergh
Title: Message The routingtable files are the rtnodes_* and rtprops_* files in your choosen freenet install folder. However.. these files occupies only a few kilobytes of your harddrive.   Is it HD space or RAM memory you want to free up?   /N -Original Message-From: [EMAIL

Re: [freenet-support] Routing table status and transient nodes.

2002-12-20 Thread Matthew Toseland
On Sat, Nov 30, 2002 at 04:33:17PM +, Roger Hayter wrote: > Can anyone explain to me the difference in success rates in contacting a > given set of nodes for a transient node from that achieved by a > permanent node? I have a permanent node which has managed to contact a > group of seed nod

Re: [freenet-support] "Routing table corrupt! Trying to reseed." throws EOFs

2002-12-20 Thread Matthew Toseland
On Sat, Nov 30, 2002 at 12:19:22AM +0100, [EMAIL PROTECTED] wrote: > Build Number 624 > > >> > 29.11.2002 23:37:58 (freenet.fs.dir.NativeFSDirectory$NWalk, main): Exhausted supply >of files29.11.2002 23:37:58 (freenet.fs.dir.NativeFSDirectory, main): > starting with D:\_freenet\store (8589934592

Re: [freenet-support] Routing table status and transient nodes.

2002-11-30 Thread Roger Hayter
In message <[EMAIL PROTECTED]>, Greg Wooledge <[EMAIL PROTECTED]> writes Roger Hayter ([EMAIL PROTECTED]) wrote: I have a permanent node which has managed to contact a group of seed nodes about 500 times after 13 trials. I would imagine something is wrong with your computer, firewall, netw

Re: [freenet-support] Routing table status and transient nodes.

2002-11-30 Thread Greg Wooledge
Roger Hayter ([EMAIL PROTECTED]) wrote: > I have a permanent node which has managed to contact a > group of seed nodes about 500 times after 13 trials. I would imagine something is wrong with your computer, firewall, network, Java VM, freenet.conf, etc. Here's what I've got on a non-transie

Re: [freenet-support] Routing Table Corrupt

2002-10-29 Thread Matthew Toseland
On Wed, Oct 30, 2002 at 10:07:59AM +1300, Wayne McDougall wrote: > Greetings. This morning I found a message Routing Table corrupt. Remote RT files and >restart. They are called rtnodes_ and rtprops_. The corruption is usually caused by a JVM bug - which JVM are you using? 1.3.1? > > I'm new - on