Re: [freenet-support] Stable build 5052

2004-01-09 Thread Edward J. Huff
On Fri, 2004-01-09 at 14:32, Niklas Bergh wrote: > Freenet stable build 5052 is now available. > > Changelog: > * tfAbsoluteMaxThreads config parameter added. > tfAbsoluteMaxThreads will allow you to limit maximum number of > threads the YThreadFactory will spawn. Default value is 500 threads.

[freenet-support] Stable build 5052

2004-01-09 Thread Niklas Bergh
Freenet stable build 5052 is now available. Changelog: * tfAbsoluteMaxThreads config parameter added. tfAbsoluteMaxThreads will allow you to limit maximum number of threads the YThreadFactory will spawn. Default value is 500 threads. This solves at least some of the OutOfMemoryError:s people

[freenet-support] Getting no mail

2004-01-09 Thread Nicholas Sturm
With your twiddling with addresses and earthlink.net twiddling with their spam blocker I am now getting no mail from freenet. Could you give me the domains that you are now using for mail? I know, that may not be enough information with those [freenet] additions in my mailbox, but perhaps we can

[freenet-support] Unstable build 6433

2004-01-09 Thread Toad
Administrative note: in future announcements of unstable builds will only go to the devl and tech lists, please subscribe to one of those lists if you run unstable. Freenet unstable build 6433 is now available. Changelog: * Fixed a major bug that was causing connections to be incapable of rece

[freenet-support] Unstable build 6432

2004-01-09 Thread Toad
Freenet unstable build 6432 is now available from CVS and the snapshots should be updated by the time you read this. The major change is the reinstatement of bandwidth limiting, in order to try to eliminate it as a major cause of network brokenness. This may well lead to a significant degradation i

Re: Fwd: [freenet-support] bug in 6430

2004-01-09 Thread Fwolff33
>> I just do not know, where to report this, (probably it was noticed already >> anyway...), but the bandwith limiting in unstable version 6430 seems to be broken: >> >> Current upstream bandwidth usage 14576 bytes/second (145,8%) >> >> And the node is not QueryRejecting or something like that and