Michael West ([EMAIL PROTECTED]) wrote: > Can you tell me what these stats mean? What is "cleanly rejected?"
> 3 were totally unreachable. > 0 restarted. > 14 cleanly rejected. The nodes you were talking to were all too overloaded to respond; or their Freenet software is not running at the moment. (I've been going on the assumption that "cleanly rejected" can mean either "the node said I'm too busy" or "the operating system said 'connection refused'".) > I have been monitoring my Success Rate and it is continually > increasing, though no documents except the one I posted can be > retrieved. It is nice to see that something is successful. You're still using the node from Debian unstable, yes? $ apt-cache show freenet-unstable Package: freenet-unstable [...] Version: 0.4.3+20020618-1 So it's from June 18th. That was before the build 474 (or 475) mandatory upgrade. It will not talk to any post-474 nodes at all; but if you can manage to find a bunch of other nodes that are as old as yours, it will happily talk to them, and you'll have a little miniature Freenet of your own. If you expect to talk to the mainstream Freenet, you'll have to upgrade to a newer build. File a bug report against the Debian package (http://bugs.debian.org/freenet-unstable) and tell the maintainer that not only does a new Freenet mandatory update (build 474) exist, but build 480 is supposed to fix important bugs. Or just replace your freenet.jar file with the latest snapshot, and restart Freenet. (This will mean that debsums won't recognize the md5sum of your freenet.jar file any longer, but that's OK as long as you don't run debsums.... ;-) ) -- Greg Wooledge | "Truth belongs to everybody." [EMAIL PROTECTED] | - The Red Hot Chili Peppers http://wooledge.org/~greg/ |
msg00859/pgp00000.pgp
Description: PGP signature
