Forwarded from Frost's freenet board:
Set up 5 nodes on 5 different ISP's. Dedicate two of them as insert
nodes, and the other three as fetch nodes.
The two insert nodes continually generate 300KB files from /dev/urandom
and insert them into Freenet. They keep track of the keys corresponding
to
Running build 6468 on Linux 2.6.2 with Blackdown-1.4.2-rc1 VM,
I get lots of temp-*-1-* files in store/temp which don't go
away after being closed. Only a node restart will delete them.
The files appear and stay even if there is no client software
running.
Getting these sporadically with 5068 on Linux 2.6.2 Blackdown-1.4.2-rc1:
11.02.2004 02:07:17 (freenet.transport.WriteSelectorLoop, Network writing thread,
ERROR): Caught java.lang.NullPointerException notifying [EMAIL PROTECTED]
MuxConnectionHandler[conn=[tcp/connection: xx.x.x.x:x,[EMAIL
Getting lots of these with build 6481, Blackdown 1.4.2-rc1 on Linux 2.6.2:
14.02.2004 00:00:00 (freenet.diagnostics.FileEventDequeue, YThread-185, ERROR): Failed
to read data from disk, using empty file.
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:268)
Running build 5074 on Linux 2.6.3 with Blackdown-1.4.2-rc1.
06.03.2004 07:24:19 (freenet.node.Node, YThread-22, ERROR): Error while receiving
message freenet.Message: Accepted @[EMAIL PROTECTED]
MuxConnectionHandler[conn=[tcp/connection: raddr:rportlocal,[EMAIL PROTECTED], [EMAIL
PROTECTED],
First they came for the child porn sites ...
http://observer.guardian.co.uk/uk_news/story/0,6903,1232422,00.html
Discussion on http://yro.slashdot.org/yro/04/06/06/132200.shtml
Blocking connections to Freenet nodes will be only a matter of time,
so what should we do to prevent them from getting
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) on Linux
2.6.7, Athlon XP. The IOExceptions are during startup, the others
when the node is running. There is also a typo in MuxConnectionHandler.java:
'utbound' rather than 'outbound'.
23.07.2004 17:40:34
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) on Linux
2.6.7, Athlon XP. After running for about 12 hours, the node dies with
this message on the console:
Unexpected Signal : 11 occurred at PC=0x4041DCFE
Function=(null)+0x4041DCFE
Since version 9.1 SuSE is using NPTL by default. To tell an application
not to use NPTL, it is recommended to set LD_ASSUME_KERNEL to 2.4.1.
You'll find a trivial patch to start-freenet.sh attached to this mail.
--- start-freenet.sh.bak2004-07-22 22:43:47.0 +0200
+++
On Sat, Jul 24, 2004 at 11:06:23PM +0100, Toad wrote:
Will be committed to unstable soon.
Having read http://people.redhat.com/drepper/assumekernel.html I think
we can do away with the distribution check and set LD_ASSUME_KERNEL to
2.4.1 for all Linux distributions. Patch for start-freenet.sh
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode) on Linux
2.6.7, Athlon XP using Athlon-optimized jbigi libs from latest
freenet-ext.jar.
Another bug(?): only transmitting connections are marked as active in
On 5 Aug 2004 04:42:44
[EMAIL PROTECTED]| (Matthew Findley) writes
| Let me see if I can get caught up on whats gone on since I left work.
| First I should probably clear this up. I am not a lawyer. I work at the
| U.S. Attoreny's Office yes; but, only as a clerk. So nothing I say is
| legal
Getting lots of these after running build 5092 for about 23 hours
with very few error messages (Sun JVM 1.4.2_05-b04 on Linux 2.6.8.1):
27.08.2004 22:41:25 (freenet.node.rt.EdgeKludgingBinaryRunningAverage, YThread-193,
ERROR): Too high probability: 1.134 while kludging [EMAIL PROTECTED] (-134
On Sat, 26 Aug 2006, Ian Clarke [EMAIL PROTECTED] wrote:
On 24 Aug 2006, at 12:01, [EMAIL PROTECTED] wrote:
Freenet 0.5 is an opennet. You connect to any random node that happens
to be on. Freenet 0.7 doesn't have this yet. In 0.7, there is no main
network. There might be now, but the idea of
you have a right to know
USK@1WZPo6qZmlCpi6rZWjtz~kig1gcpcnzh5drmqpW9L8Q,ksaFFDkSJfnOXB3ppYhQ2R14z3W
QCYxGqXNERCYcHD0,AQACAAE/wordsoftoad/-1/
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
On Sat, 26 Aug 2006, Ian Clarke wrote:
>On 24 Aug 2006, at 12:01, urza9814 at gmail.com wrote:
>> Freenet 0.5 is an opennet. You connect to any random node that happens
>> to be on. Freenet 0.7 doesn't have this yet. In 0.7, there is no main
>> network. There might be now, but the idea of the way
(please excuse me if this is a duplicate)
Toad,
Recently a message by you was xposted to 0.5 about a crypto weakness you folks
discovered in 0.7 that 0.5 is also subject to.
After some discussion, one individual came up with a patch and procedure for
fixing this on 0.5. While a lot will
In my earlier request for the crypto fix build for 0.5, I forgot to ask if
you'd also be willing to incorporate the "painkiller" mods in 5108?
Thanks again
18 matches
Mail list logo