On Tue, Oct 29, 2002 at 04:58:00PM -0400, Doug Bostrom wrote:
On Tuesday 29 October 2002 01:55 pm, you wrote:
Use the bandwidth limiter to prevent it swamping your connection. It is
expected to use lots (up to 120) threads - they should normally be
almost all idling. The current
Greetings,
Checking my node this morning, (after waiting for top to come up, swap swap swap) I
found I had some 155 java
processes going. Any way to control this? Right now I can either run a node or work,
not both. Maxnodeconnections
seems to have no effect on the number of connections the
On Tue, Oct 29, 2002 at 08:47:42AM -0500, Doug Bostrom wrote:
Greetings,
Checking my node this morning, (after waiting for top to come up, swap swap swap) I
found I had some 155 java
processes going. Any way to control this? Right now I can either run a node or work,
not both.
On Tuesday 29 October 2002 01:55 pm, you wrote:
Use the bandwidth limiter to prevent it swamping your connection. It is
expected to use lots (up to 120) threads - they should normally be
almost all idling. The current situation is a product of the network
being slashdotted, and
On Tue, Oct 29, 2002 at 04:58:00PM -0400, Doug Bostrom wrote:
On Tuesday 29 October 2002 01:55 pm, you wrote:
Use the bandwidth limiter to prevent it swamping your connection. It is
expected to use lots (up to 120) threads - they should normally be
almost all idling. The current
Similar problem - I am seeing a vast number of open sockets - all listening
on bound to 0.0.0.0:8481 and listening for connections - but not seeing any
traffic.
Surely there should only be one socket open listening on that port?
I also seem to be seeing extremely low transfer rates on all of
