Dashkal <dashkal at ...> writes: > > Ok, strange thing > > This time I didn't kill freenet when it appeared to hang when asking me > to enter the port number. > > When I took the time to start this email, it eventually unhanged itself > and started to work.
--snip for over-zealous gmane filter-- > 'freenet/support/CPUInformation/libjcpuid-x86-linux.so' loaded from resource > INFO: Optimized native BigInteger library > 'net/i2p/util/libjbigi-linux-athlon.so' loaded from resource > <<<--- This is where it hung --->>> > 62734 > listenPort [19934] Don't disclose your listenPort, since it can be used to identify your node with some degree of confidence :) I'd change it now if I were you. --snip for over-zealous gmane filter-- > tail -f freenet.log <<<--- My input to that $ prompt above --->>> > Apr 10, 2006 4:30:52 PM (freenet.node.Main, main, NORMAL): Starting > Freenet (Fred) 0.5 node, build #5106 on JVM Blackdown Java-Linux > Team:Java HotSpot(TM) Client VM:Blackdown-1.4.2-03 > <<<--- Hangs here --->>> > Apr 10, 2006 4:33:35 PM (freenet.node.Main, main, NORMAL): loading node > keys: node > Apr 10, 2006 4:33:35 PM (freenet.node.Main, main, NORMAL): Creating node > keys: node > <<<--- SNIP --->>> > > From there it appears to work. I am able to connect to the proxy port > as normal. Yeah, this is actually a known issue with 0.5 but it's supposed to be kind of fixed. I thought it was only people like with weird setups (blackdown 1.4.1 / sparc64) who still saw huge pauses. A similar problem seems to be affecting 0.7 judging by recent posts. What's actually happening is that the Yarrow PRNG is blocking whilst waiting for enough entropy to be collected, so that it can generate somewhat "strong" psuedo-random numbers (important to stop attacks on encryption.) If you have a true hardware RNG e.g. a VIA C7 processor or dedicated crypto card then IIRC it just reads /dev/hwrandom and off it goes, but most people don't. So it has to read /dev/urandom or /dev/random (forget which) which generate psuedo-random numbers based on unpredictable 'entropy' activity like mouse movements, keypresses, and hard disk activity. Therefore you should be able to speed it up by opening a text editor and mashing the keyboard randomly, waving the mouse around, doing disk searches etc. This is a bit daft but there's no real way around it, short of everyone buying proper RNGs. Other crypto apps like GPG have the same problem at key generation time and likewise ask you to type randomly / wave the mouse around. Bob
