Re: [freenet-support] Is it always this slow?

2004-12-04 Thread S
Can't we all just get along? Newsbyte maintains the freenethelp.org site, right? Isn't that enough of a contribution to render his opinions (however blunt they may be) welcome? For that matter, shouldn't opinions be welcome regardless of contribution? These questions are not directed at anyone

[freenet-support] regarding freenethelp.org slowness

2004-12-04 Thread Grant Supp
I've noticed the Freenethelp.org wiki site is VERY slow and would like to help improve it's speed. Can you put me in touch with who is responsible for maintaining the site? I work for an ISP, as well as willing to donate hardware or money to help the site. I feel the freenethelp.org site is

Re: [freenet-support] Is it always this slow?

2004-12-04 Thread Toad
On Sat, Dec 04, 2004 at 08:42:10AM -0600, S wrote: Give it a fucking rest, already, and let's get back to making Freenet better. That is just the problem. Newsbyte's core argument is that the ONLY way to make Freenet better is to abandon Freenet and implement something completely different (oh

Re: [freenet-support] What is this consequitive same winner thing?

2004-12-04 Thread Toad
Could be a bug, could be severe CPU overload. On Thu, Dec 02, 2004 at 08:44:52PM -0800, Nick wrote: Recently I started getting Consecutive same winner messages in my event log. It mostly happens when I try to download something big (around 700mb). Any hint what could this mean? I am

[freenet-support] Re: What is this consequitive same winner thing?

2004-12-04 Thread Someone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Toad schrieb: | Could be a bug, could be severe CPU overload. I tend to say it's a bug. I get many of them since 5099, and this even on my 1,8 GHz machine. The average CPU load with freenet is around 10% on this machine with no spikes above 40%, so I

[freenet-support] Consecutive same winner

2004-12-04 Thread Sara Mill
Does this seem right?? using 5100 stable; uptime 15 hours: grep -c Consecutive freenet.log :== 14512 wc -l freenet.log :== 46269 Connections open (Inbound/Outbound/Limit) 32 (8/24/40) Transfers active (Transmitting/Receiving) 45 (11/34) Uptime: 0 days, 14 hours, 50 minutes