I have changed something in the clients that won't allow the same bug to occur after I commit, but something is still definitely FUCKED UP with your box man.
All these bugs are the results of Connections failing left and right on you, something that just shouldn't happen when connecting locally, and that since I have never seen before I have a hard time believing is Freenet's fault (also the fact that they are coming and going and happening in different places). What you should do is add a StackTrace on line 28 of Freenet.transport.tcpConnection to see exactly what kind of IOException is occuring. What JDK are you using? What satanistic spells have you performed on your computer recently? What sort of distruptive software did those NSA agents install when they broke in while you were sleeping? On Sat, Aug 19, 2000 at 02:43:07PM +0100, Ian Clarke wrote: > Still playing around (this time with test5.sh) and I stumbled across > another exception. Looking at the node logs it seems like the data > may have been stored, but the client winds up in a "FAILED" state so I > thought I should mention it just in case: > > Client log: -- \oskar _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
