Re: [freenet-support] Port 8081 already used by another application

[Ruediger Kapitza]

On Wed, 30 May 2001, Greg Wooledge wrote:

 Perks, Graham ([EMAIL PROTECTED]) wrote:
  BTW, is it reasonable for Freenet to be used as a team-private super shared
  drive?  For example, have one Freenet system with disk space spread over 10
  nodes, running on a particular port separate from the open-to-anyone
  worldwide Freenet?
 
 I suppose you could do this, but you might need to disable the announcement
 that goes to the inform server.  I'm not sure how best to do that.

I think that's all (freenet.ini or .freenetrc) :

# Should we read some information about other nodes from the informUrl?
informRead=no

# Should we write our address to the inform URL so that others might
# find out about us more easily?
informWrite=no  

and a valid file with your private nodes ..

# The name of a file containing an initial set of nodes to connect to
nodeFile=nodes.config


Ruediger


___
Support mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/support

Re: [freenet-support] 0.3.9.1+IBM 1.3 JDK+Linux 2.2.14 = Splat?

[Ruediger Kapitza]

On Wed, 30 May 2001, Doug Bostrom wrote:

 Wondering if anybody else has seen this. I've been running 0.3.9.1 on i386 Linux 
2.2.14 w/ IBM JDK 1.3. successfully since 0.3.9.1 was released. Tons of traffic, lots 
of 
 storage and retrieval happening, everything seemed to be working smoothly. A couple 
of days ago the box the whole affair was running began locking hard- no console 
 access, ethernet unresponsive, etc. This happened several times, but stopped when I 
reluctantly shut off the freenet facility. Crashes happened within 1 hour of 
 restarting the box. Notify time is set to 15 mins (and I hope I've not violated any 
sanctions with that).
Hi!

Have you set a useful limit for incoming connections ?

# Should we use thread-management?  If this number is defined and 
#non-zero,
# this specifies how many inbound connections can be active at once.
maximumConnectionThreads=50

If this value is not set in .freenetrc than there could be so
many incoming connections and this means threads and this maybe means
native thread(== processes) that it may exceed the system limit.

Another reason could be that you 
a) insert to much into freenet through a script
or 
b) request many things through fproxy

If b is the case you could try to run fproxy in a new jvm
and disable it in the config file.

All just guesses ...
Ruediger



___
Support mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/support