Geir Granum wrote:
Geir Granum wrote:
snip myself
they are all (apart from 1) inbound. From a node running 5028 according
to nodestatus.
now nodestatus reports 24 inbound from a node running 6194 (which
shoudn't do that?)
tcp/216.103.210.58:18715 0.30737418 none 11 2
I recently upgraded my node to 6194 and since then I've been getting a
really huge send queue which just gets bigger since I've got only 64kbps
upstream bandwidth.
My node has been running for less than 11 hours and my send queue is at
179MB waiting to be transferred.
Also, I'm getting way more
Toad wrote:
The downside of non-probabilistic caching was not that the nodes always
put the data into their cache. This just caused data to be dropped
that was equally unimportant. Pcaching will drop the data, even if
there are still gigs of free space left in the data store.
No it won't. Well,
When I was seeing sporadic JVM chrashes it was because a faulty memory
module in the computer (except when toad tried our DirectByteBuffers for
network I/O)...
/N
- Original Message -
From: Gordan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, September 13, 2003 3:52 PM
Subject:
When I was seeing sporadic JVM chrashes it was because a faulty memory
module in the computer (except when toad tried our DirectByteBuffers for
network I/O)...
/N
- Original Message -
From: Gordan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, September 13, 2003 3:52 PM
Subject:
Where can I get all of these fancy new freenet versions that this
devel-list keeps referring to? The sourceforge CVS seems to be stuck at
6173 for its unstable branch.
Messages here on this list allude to versions of freenet that do *not* peg
the CPU to 100% with a load average 10 (RH9-x86/Sun
Acid06 wrote:
I recently upgraded my node to 6194 and since then I've been getting a
really huge send queue which just gets bigger since I've got only 64kbps
upstream bandwidth.
My node has been running for less than 11 hours and my send queue is at
179MB waiting to be transferred.
I may be
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
Where can I get all of these fancy new freenet versions that this
devel-list keeps referring to?
http://freenetproject.org/snapshots/ (look for freenet-latest-unstable.jar
or freenet-unstable-latest.jar, I forget which).
The sourceforge CVS seems
pineapple [EMAIL PROTECTED] writes:
I was wondering if there were any plans to have the
option in Freenet for users to make their node read
only. That is, content can only be inserted localy
and not by requests. Some content providers may want
to make their material available permanently
On Sun, 14 Sep 2003 [EMAIL PROTECTED] wrote:
Where can I get all of these fancy new freenet versions that this
devel-list keeps referring to? The sourceforge CVS seems to be stuck at
6173 for its unstable branch.
Latest unstable:
There seems to be a major problem with 6194 starting more trailers than
the node it is on can possibly send, this resulting in node overload and
freenet.broke hopefully toad'll fix it monday... Until then, 5028 or
6163 I think are the builds to use if you need good browsing.
--Brandon
On Sun,
On Sun, Sep 14, 2003 at 10:53:41AM -0700, [EMAIL PROTECTED] wrote:
Where can I get all of these fancy new freenet versions that this
devel-list keeps referring to? The sourceforge CVS seems to be stuck at
6173 for its unstable branch.
Are you doing an ant clean before recompiling CVS?
Ian.
On Sun, 14 Sep 2003, Edgar Friendly wrote:
pineapple [EMAIL PROTECTED] writes:
I was wondering if there were any plans to have the
option in Freenet for users to make their node read
only. That is, content can only be inserted localy
and not by requests. Some content providers may
But would anyone ever find anything on the read-only node? Say I've got
200 items on the read-only note (ie, a couple moderate-sized websites).
Chances are there will be no similarity between the CHKs of those items.
(And furthermore the CHKs will bounce around wildly as the content is
On 2003-09-14 at 20:49, Brandon Low wrote:
There seems to be a major problem with 6194 starting more trailers than
the node it is on can possibly send, this resulting in node overload and
freenet.broke hopefully toad'll fix it monday... Until then, 5028 or
6163 I think are the builds to use
I'm new to looking into the Freenet code and haven't got the full
picture of workflow, but I know it isn't pleasant.
The good news is I'm running with Windows ME MaxConnections set to 256
and freenet's max connections up to 128 without any additional bugs.
The squeamish should close their eyes
16 matches
Mail list logo
