Yes, the problem is in the stable branch too and Toad already said that it's been widely reported and they hope that NG routing will fix it. You might as well take your node down until NG is released or go back to an old version.
----- Original Message ----- From: "Gordan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 20, 2003 11:20 PM Subject: [freenet-dev] Broken Versions > Is it just me, or is there no version of unstable Fred since 6148 that > actually works? > > All versions since then (or thereabout - the next one I have is 6154) seem to > get stuck at routing time of 0ms, exceed the threat limit, and stay there > doing nothing except using up CPU time and memory. No bandwidth usage at all. > > Has anybody else noticed similar behaviour? What has gone into Fred around the > 6149/6150 mark that could explain this? > > Gordan > _______________________________________________ > devl mailing list > [EMAIL PROTECTED] > http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl > > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
