|
Thanks for the suggestion, Kevin, but I've been running with
"max-connections" set to 200, and "max-connections-per-server" set to 100. So
that shouldn't be the problem, right?
Someone else suggested setting "threadFactory" to "Q", rather than the
default. I'm trying that.
----- Original Message -----
Sent: Thursday, December 11, 2003 9:37
PM
Subject: Re: [freenet-support] Sometimes
can't get to my own node's data
On Fri, 2003-12-12 at 04:49, Art Charbonneau wrote:
> I'm
running 5050 on ADSL, 2.4 GHz, with Outgoing set to 30,7200 B/s,
> CPU
set to normal priority, and store set to 1 gig.
>
>
Sometimes Freenet starts up quite normally (for this period in time)
>
and I can get to a few freesites (mainly using bookmarks, in Netscape
>
7.1), but then I'll go back to the Web Interface to look at info and
>
stats, and I can't get to my own node (like right now).
This sounds
most like you're hitting the limit of connections in your
browser. If you
have one browser window open trying to retrieve images
for a page (e.g. The
Freedom Engine) then your browser will wait for
those connections to finish
before trying to download the web interface
page.
If you are
running Opera or a Mozilla-based browser, there are
instructions in the
Freenet README file on how to extend the number of
connections your browser
uses per
server.
-Kevin
_______________________________________________
Support
mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
|
_______________________________________________
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
