Leland Lucius reported a problem where /dev/urandom was returning 0 bytes on a read. Well, it bit us too. I filed a support call with Novell/SuSE and got "if you can't give us a system where the bug is happening now, we can't help." Unfortunately I'd run Leland's little C program to fix it. Novell/SuSE couldn't find any reports of this in their bug database. Has it happened to anyone else? What distribution are you running, and what kernel? (It's SLES 11 SP2 and 3.0.58-0.6.6-default for us.) So far it's only happened on one server, and the consequences have been fairly minor. But of course until we understand what triggers it we're a little nervous about it. I'll summarize any answers sent directly to me. Thank you. Ted Rodriguez-Bell, [email protected] Company policy requires: This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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/
