9 Jun
2010
9 Jun
'10
2:29 p.m.
It was as you suspected.
The init script is now being used.
Thanks.
On 9 June 2010 11:45, Andy Smith <andy(a)bitfolk.com> wrote:
Hi Robert,
On Wed, Jun 09, 2010 at 11:09:02AM +0100, Robert Gauld wrote:
--
Robert Gauld
http://www.robertgauld.co.uk
Just want to check I'm not missing
something.
watch --interval 0.5 cat /proc/sys/kernel/random/entropy_avail shows
numbers
between 120 and 180.
So I:
sudo aptitude install ekeyd-egd-linux
sudo iptables --append OUTPUT -p tcp --dport 8888 -d 212.13.194.102 -j
ACCEPT
sudo ekeyd-egd-linux -H 212.13.194.102 -p 8888 -b 2 -r 10 -D
/root/entropy
netstat shows the expected connection as established, yet watch
--interval
0.5 cat /proc/sys/kernel/random/entropy_avail
behaves in the same way.
I'm convinced I'm missing a step but can't see it, can any one else?
What does:
sysctl kernel.random.write_wakeup_threshold
say?
This is the level at which the kernel asks for more entropy. By
default it tends to be 128. The init script for ekeyd-egd-linux
(which you aren't using) sets it to 1024 by default. Feel free to
set it at 4000 or so if you like.
sudo sysctl kernel.random.write_wakeup_threshold=4000
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users