DigitalE wrote:
> Request for comments:
>
> New variable:
> Peak Specialization (PS)
> Nodes look for a peak in their datastore around a
certain key and store
> its position as their Peak Specialization (PS) which
is advertised to
> other nodes whenever a connection is made and stored
in routing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
| If you respond saying 'I would run one', please
include the following
| basic stats:
| Bandwidth (approx)
| Disk space (approx)
| Available memory (more logging => more memory usage,
sadly... under some
| situations we would need more lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
| One radical proposal that I think might be quite
useful:
|
| We reinstate something in the spirit of the watchme
network. Since
| everything is tracked, there is no anonymity, so it
would only be used
| for testing i.e. exchange of legal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tracy R Reed wrote:
| On Tue, Dec 02, 2003 at 09:04:28PM -0500, Zlatin
Balevsky spake thusly:
|
|>a) I would run a node without anonimity and let the
devs get all info
|>they want, and would stick around to assist them
|
|
| A.
|
A here too !
-B
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On DSL Reports (http://www.dslreports.com) there is
currently an article
on anonymous file trading, it doesn't offer any
insight, but many of the
people there have never heard of Freenet, and I'm sure
they'd appreciate
the insight of the users/develope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
fish wrote:
| On Tue, Nov 25, 2003 at 01:12:04AM -0800, Salah
Coronya wrote:
|
|>data to go because everyone's link is saturated). I
|>propose in the
|>"unstable" (or maybe re-opening the "experimental")
|>b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well so far routing doesn't seem to have improved,
most requests are
failing (51051 requests attempted, 409 succeeded; 514
inserts
attempted, 7 succeeded). About 14000 qph here.
Its been brought up several times the reason NGR might
not appear to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
| On Fri, Nov 21, 2003 at 02:25:08PM -0600, Tom Kaitchuck wrote:
|
|>On Tuesday 18 November 2003 04:36 pm, Tracy R Reed wrote:
|>
|>>On Tue, Nov 18, 2003 at 09:18:51PM +, Jonathan Howard spake thusly:
|>>
|>>>I think freenet is suffering
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Niklas Bergh wrote:
|>|>> This has nothing to do with load balancing, but should improve
|>|>> routing, while increasing CPU usage by some unknown amount. Thoughts?
|>|
|>|
|>| Actually this has A LOT to do with load balancing, indirectly.
|>| Given t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Corson wrote:
| Martin Stone Davis wrote:
|
|> Martin Stone Davis wrote:
|>
|>> We start at the top of the list, and see who is going to make our
|>> will the fastest. Since our lawyer is "backed off" at the moment, we
|>> go with our chef.
|
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
| On Fri, Nov 14, 2003 at 10:29:24PM -, Simon Porter wrote:
|
|>Home users on the other hand generally don't turn off UPnP :P
|
|
| Indeed. We found a free implementation in java, but it looked rather
| generic, we would need documentat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Currently, those of use whom are NAT'ed have to configure ipAddress
manually. If ones IP isn't very sticky (and/or is not using dynamic
DNS), it can be a pain to keep changing it. So I have a simple solution:
Why not just ask the node were connecting to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Stone Davis wrote:
| Mike Stump wrote:
|
|> keys: 1739
|> scale factor: 0.08205128461122513 (This is used to
keep lines < 64
|> characters)
|>
|>0 |=
|>1 |=
|>2 |=
|>3 |==
|>4 |===
|>5 |
|>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been running 6323 (compiled from CVS), for 15 1/2
hours and my node
seems to be processing a lot more requests:
Histogram of requested keys.
This count has nothing to do with keys in your
datastore
Nov 10, 2003 12:07:57 PM
keys: 198031
Histogram
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tracy R Reed wrote:
| On Sun, Oct 26, 2003 at 02:08:20PM +0100, Niklas
Bergh spake thusly:
|
|>I am pretty sure that toad will do this for any
coming stable builds.
|>Hopefully stable releases will be re-indroduced soon
:)
|
|
| But please, let's not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
J wrote:
| Quoting "Edward J. Huff" <[EMAIL PROTECTED]>:
|
|
|>It would be interesting to see the node version histogram
|>of people who are getting good performance.
|
|
| I'm getting 'decent' performance. Much better than late, but not the
best i've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Stump wrote:
| I'm still seeing:
|
| java.io.IOException: Already closed!
| at freenet.ConnectionHandler.(ConnectionHandler.java:283)
| at
freenet.OpenConnectionManager$ConnectionJob.run(OpenConnectionManager.java:1423)
| at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Conrad J. Sabatier wrote:
| I've been unable to connect to cvs.sourceforge.net all day. Anyone else
| experiencing this?
|
| Also seeing some weird junk in the connection refused message, like:
|
| cvs [update aborted]: unrecognized auth response from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
J wrote:
|
| I disagree. Exactly ZERO development effort should be put into this.
~ Find a
| build that works well in the 5xxx series and stick with that IMO.
|
Then it probably should be 5028.
~From build 5015-5020, insert were broken (you could ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Stone Davis wrote:
| 6223 definitely seems better than 6222. But, I did get an error and
| stack dump soon after starting it. See attached.
|
Its not just you:
Oct 7, 2003 3:56:13 PM (freenet.PeerPacketMessage, write interface
thread, ERRO
R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
| Okay, what should we set the unstable lastGoodBuild to?
|
Someone on here if you're going to run unstable, use at least build
6215, so how about that build?
Or maybe a different scheme could be used? Perhaps some kind of "version
affinity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salah Coronya wrote:
| 9. In previous version of Freenet, if I keep it running (4 hours or so
| with 6221), I'll eventually get "Out of file descriptor" exceptions. I'm
| pretty sure the same will happen again (we'll see).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well non splitfile downloads and all inserts now work in 6222. Inserts
are MUCH faster. Splitfile inserts no longer hang (well, almost - I
inserted a 148 block file (after FEC encoding, and it stalled with 2
blocks to go. I let Fuqid time them out and i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
| Unstable 6221 fixes a major bug that was making local inserts appear to
| take forever, and never generating a StoreData for remote inserts.
| Anyone running the unstable branch should upgrade. The snapshots have
| been rebuilt. Apologies
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
| What was maxNodeConnections? What was your local query traffic?
|
maxNodeConnections is 512.
Local query traffic (as of 6221 is about 10,000)
I noticed in 6221 it now displayed the "request quota". As it turns out,
I was exceeding by a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Lamont wrote:
| On Sunday 05 October 2003 12:00, Martin Stone Davis wrote:
|
|>Richard Lamont wrote:
|>
|>>On Sunday 05 October 2003 10:33, Martin Stone Davis wrote:
|>>
|>>>The developers probably already know this, but I'm posting anyway.
|>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edward J. Huff wrote:
|
| is committed, but it was merged with 6217 changes.
|
| I've been watching netstat for connections with nonzero queues.
| Many of them stay around for hours. Some have nonzero input
| queues: no one is reading the data, which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just grabbed and compiled 6216 off CVS:
One of the new features is to list the port number in the "Open
Connections" screen, but a few (1 or 2) have port 0 listed! I can't find
~ them anywhere in "netstat" either. (Incidentally, as a cosmetic effect,
c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
|>I've noticed some the previous builds (like 6205) were slow on splitfile
|>inserts (and tended to hang on the last couple of blocks), but latest
|>ones I can let a splitfile insert run overnight and not even get ONE
|>block inserted.
|
|
Tracy R Reed wrote:
I've been holding off on sending this email for ages but I'm sitting here
for the zillionth time looking an insert that is going nowhere preventing
me from inserting the kind of legal and legitimate content that freenet
needs to survive and my frustration level is getting the b
Ian Clarke wrote:
Well, thinking about it what is there is:
not(connectFailed) and not(searchFailed)
My suggested correction was:
not (connectFailed or searchFailed)
Which, if I am not mistaken, is the same thing.
So n/m.
Ian.
Yep, DeMorgans thoerem.
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| I checked my rtnode_a and rtnodes_b file, and look what I found
|
| 'Õ^T?N
| version=] ^Rbª^5^QãÇâ,5028
| presentations=1
|
identity.g=930168de21e7fb66c0375e08e964255a0f7f0ad54507a51864afdc686f36be8bb8b7$
|
| identity.q=ef1f7a7a73362e526515f348075aee2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tracy R Reed wrote:
|
| I have this and I saw someone on IRC with this also. I suspect a node out
| there was handing out a corrupted noderef and now a bunch of us have it.
| Any easy way to figure out which node it is so we can remove it? Not a big
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Stone Davis wrote:
| Okay, I'll change back to maxRequestsPerInterval=300, re-activate
| bwlimiting, and upgrade to version 6211. My machine has 512MB of RAM,
| so I will set JavaMem=256.
|
| -Martin
|
| Brandon Low wrote:
|
|> How much ram doe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Stone Davis wrote:
| As you probably read in the "Decreasing upstream bandwidth over time in
| 6205" thread, I've been having the same kind of problem. (note: I am
| now using 6209)
|
| It turns out that my QueriesPerHour is very high, like Sal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon Low wrote:
| Threadlimits probably aren't the issue any more, can you check how many
| queries per minute your node is accepting? There is a default in the
| config file to only accept a max of 300 queries per minute, is it
| possible that that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In build 6209 (and as far back as 6206/7), splitfile inserts are
painfully slow, to the point of where I though they weren't working at
all, but somehow I actually manager to get a block inserted (at HTL=25,
build 6209) . Even at HTL=1, splitfile insert
David McNab wrote:
Maybe I could take this approach
- if prog can do fcp handshake on port 8481
- freenet is found
- else
- browse 'network neighbourhood' to get hostnames of
other boxen in lan
- if prog does successful FCP handshake with one of those other boxen
on the LAN
Edgar Friendly wrote:
Those dialog boxes *must* default to localhost/8481, of course. For
the many people who are trying it out locally.
Thelema
Yep, just prompt for the node address on install, filling in
localhost/8481 by defualt. In order to get Freenet to take FCP requests
from others ho
David McNab wrote:
On Wed, 2003-09-24 at 11:17, Toad wrote:
What build number?
Oops - sorry - 5028
Try build 6205, it seems to work better - non-local FCP connection no
longer hang and actually get data.
___
Devl mailing list
[EMAIL PROTECTED]
http:
Toad wrote:
Well, is it fixed in current unstable?
Well, I'm using build 6205, and I can now use FCP over non-localhost
interfaces again, so it seems to be working now.
___
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mail
fish wrote:
As has been previously discussed, this problem does not effect everyone,
and often only effects the people whom it does intermittantly, coming and
going.
Well, I can reproduce it 100% of the time. I tried going through the
Freenet sourcecode, but it is simply HUGE, and the Sourcef
David McNab wrote:
Again, something has crept into the node code between build 5013 and
5028 which is causing this fatal weirdness.
Clues?
Between Freenet build 5020 and 5021, FCP would no longer function
properly on anything other than localhost (not matter WHAT fcpHosts was
set to)- the client
Toad wrote:
Would you please try unstable build 6180? It _might_ have fixed this
problem recently.
[snip]
Now using unstable build 6183. Problem still there, even data at HTL=0!
. Localhost (via an ssh tunnel) works.
___
Devl mailing list
[EMAIL PROTEC
As of build stable 5021 (5020 was the last one that worked), no
splitfile downloads (anywhere except FProxy - neither Frost nor Fuqid
would work) worked nor splitfile uploads (at least in Frost - the file
would get to 100% and Frost would throw a NullPointerException) worked.
Any attempt to ab
45 matches
Mail list logo
