On 5/16/2013 10:15 AM, Will, Chris wrote:
> We ran into this issue and are rolling out the fix provided by Novell.
> Novell was telling us that it was due to a large number of ssh logins to a
> host but this does not always seem to be the case. Anyone have a more
> definitive reason for what caused the error and how it was fixed?
>
The ssh thing is just a way to recreate the problem. It's really just a matter
of multiple simultaneous users of /dev/urandon and ssh was one way to do it. I
was able to recreate it with:
#!/bin/sh
for ((c=0; c < 32; c++))
do
for ((i=0; i < 256; i++))
do
dd if=/dev/urandom of=/dev/null bs=1 count=4096 >/dev/null 2>&1 &
done
done
dd if=/dev/urandom of=/dev/null bs=1 count=1 2>&1 | grep -q '0 bytes' && echo
"badness"
exit
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
