> Fix (hopefully) for the problems which were reported with a node
> getting 120 connections and then becoming unresponsive with no
> traffic. OpenConnectionManager.put() should kill enough connections to
> take us back under the connection limit, not search for enough and
> then only kill one
Build 659 is now in CVS. Within a few hours it should also be available
as the current unstable snapshot. Features:
* Avian's latest HTML filter fixes (thanks!)
* Fix (hopefully) for the problems which were reported with a node
getting 120 connections and then becoming unresponsive with no
traf
On Tue, Feb 04, 2003 at 03:08:26PM +0100, Niklas Bergh wrote:
> >From my console:
>
> YOUR NODE CAUSED THE HEISENBUG - PLEASE REPORT SETUP TO FREENET DEV
> MAILING LIST!
> PANIC! Just recreated heisenbug! ID: 1d47d9431d47d943
> YOUR NODE CAUSED THE HEISENBUG - PLEASE REPORT SETUP TO FREENET DEV
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 04 February 2003 08:57 pm, Matthew Toseland wrote:
> On Mon, Feb 03, 2003 at 12:16:02PM +0100, [EMAIL PROTECTED] wrote:
> > At 00.57 03/02/03 +, you wrote:
> > > Re [freenet-support] freesite .ems > > [freenet-support] freesite .ems <088
On Mon, Feb 03, 2003 at 06:49:53PM -0500, Greg Wooledge wrote:
> Wow, build 546 is so good it can make connections to nodes without
> even trying!
>
> Contact Failure ConnectionSuccessful
> Address Probability Interval Attempts Connecti
On Tue, Feb 04, 2003 at 12:34:29AM +0300, Victor Denisov wrote:
> I'm sorry, I'm still to receive a single message from support mailing
> list... To continue discussion:
>
> ---
> >> Of course, all outgoing ports are open for an IP address that Freenet is
> >> bound to. The pro
On Mon, Feb 03, 2003 at 12:16:02PM +0100, [EMAIL PROTECTED] wrote:
> At 00.57 03/02/03 +, you wrote:
> > Re [freenet-support] freesite .emsfreesite .ems <0880.0002>>
> >
> >Personally I have never used Frost mainly because it uses Swing, which
>
> I'm using FIW, a swing application, with Kaff
Could you possibly get a stack dump? kill -QUIT `cat freenet.pid` (the
pid of the top java process for the node). It is _possible_ that this is
some sort of deadlock.
On Tue, Feb 04, 2003 at 01:51:37PM +0100, Niklas Bergh wrote:
> I would like to reinforce my previous speculation.
>
> One of my m
Just noticed that the previously-hosed formatting on my freesite is back to normal now. Fproxy isn't mangling the html anymore. Nice job, guys! :)
-- MB
___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/s
Sorry for the loss of formatting, I hope that someone manages to read it
anyway :(
/N
___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
>From my console:
YOUR NODE CAUSED THE HEISENBUG - PLEASE REPORT SETUP TO FREENET DEV
MAILING LIST!
PANIC! Just recreated heisenbug! ID: 1d47d9431d47d943
YOUR NODE CAUSED THE HEISENBUG - PLEASE REPORT SETUP TO FREENET DEV
MAILING LIST!
PANIC! Just recreated heisenbug! ID: 48797ce348797ce3
YOUR N
I would like to reinforce my previous speculation.
One of my machines are running a v551 fred node, current uptime is about
6 days. The machines processor usage is somewhere around 10 percent or
so but fred is reporting 90-95 percent load and freds network usage is
close to zero. Fred has a consta
12 matches
Mail list logo