Go to http://127.0.0.1:/servlet/nodestatus/nodestatus.html and
click the Download References button. Rename the resulting file
from noderefs.txt to seednodes.ref.
try setting Minimum successful connections to 0 before clicking on the
download button, so you get all yet unconnected
Secret options are bad :) I still seem to have
an un-needed 'temporary directory' setting -
which it warns me about on every startup.
Can you expound on this one?
28-Oct-02 17:26:01 (freenet.node.Main, main):
WORKAROUND: Ignoring obsolete fproxy.* lines in
freenet.conf/ini. You can remove
Dammit. System crashed, and the databugs ate my routing table again.
A thousand thousand blessings upon the person who explained how to export my routes :)
Upgraded to 531 (since I crashed, I might as well)
___
support mailing list
[EMAIL PROTECTED]
- Original Message -
From: Vitenka - Zen [EMAIL PROTECTED]
Nodeconfig refuses point blank to run on my machine as of main build 529.
* make it so that nodeconf can change every option
Secret options are bad :) I still seem to have an un-needed 'temporary
directory' setting - which
* fix import/export ref on bunny
Can we have an export all known references option? At least until the
routing table stops getting eaten by the datastore bugs :)
Go to http://127.0.0.1:/servlet/nodestatus/nodestatus.html and
click the Download References button. Rename the resulting
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
Go to http://127.0.0.1:/servlet/nodestatus/nodestatus.html and
click the Download References button. Rename the resulting file
from noderefs.txt to seednodes.ref.
try setting Minimum successful connections to 0 before clicking on the
Excellent! Build 530 CPU usage is WAY down! Great job! Just curious what
changed to improve performance?
___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Ahhh ... oops! Couple hourse later, freenet is back up to 100% CPU. My
excitement was premature :(
- Original Message -
From: Robert Carroll [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 04, 2002 6:54 PM
Subject: Re: [freenet-support] windows 0.5.0.4 monolithic
Nodeconfig refuses point blank to run on my machine as of main build 529.
* make it so that nodeconf can change every option
Secret options are bad :) I still seem to have an un-needed 'temporary directory'
setting - which it warns me about on every
startup.
* have nodeconf just edit the
Vitenka - Zen ([EMAIL PROTECTED]) wrote:
* fix import/export ref on bunny
Can we have an export all known references option? At least until the
routing table stops getting eaten by the datastore bugs :)
Go to http://127.0.0.1:/servlet/nodestatus/nodestatus.html and
click the Download
Am 01.11.2002 04:17:56 schrieb Mathew Ryden [EMAIL PROTECTED]:
I've uploaded the monolithic installer incase anyone actually uses that
horrific thing (actually, an amazingly large amount of the freenet installs
have been the monolithic installer)
I've tried to install one (running a small second
GrimHunter ([EMAIL PROTECTED]) wrote:
Am 01.11.2002 04:17:56 schrieb Mathew Ryden [EMAIL PROTECTED]:
I've uploaded the monolithic installer incase anyone actually uses that
horrific thing (actually, an amazingly large amount of the freenet installs
have been the monolithic installer)
I've
I've uploaded the monolithic installer incase anyone actually uses that
horrific thing (actually, an amazingly large amount of the freenet installs
have been the monolithic installer)
Anyways, the new installer is up, with no changes over the last monolithic
installer (0.5.0.4-2).
Hmm - I don't
13 matches
Mail list logo
