On 3/18/04 3:39 PM, "turgut kalfaoglu" <[EMAIL PROTECTED]> wrote:
> Well, even after I disable urandom, which my system does not have anyway, > I still have clamd hanging; eating up over 90% of the CPU, and doing > nothing basically. > I am trying daily builds, but it does not help. This sometimes happen > after five minutes of runtime, but sometimes with just 2 minutes of runtime. Well I wish I could help. So far (knock on wood) since I compiled with --disable-urandom on FreeBSD clamd has been running on several servers so far without a "hang". I won't say this problem is solved until I see it run a day or two without doing so. We have it running on some fairly busy production servers so we'll see... Have you tried compiling with "--enable-debug" and running clamd in debug with verbose logging? Maybe that may shed some clues before having to do a full KTRACE on it... -- Robert Blayzor, BOFH INOC, LLC [EMAIL PROTECTED] PGP: http://www.inoc.net/~dev/ Key fingerprint = 1E02 DABE F989 BC03 3DF5 0E93 8D02 9D0B CB1A A7B0 A bad random number generator: 1, 1, 1, 1, 1, 4.33e+67, 1, 1, 1 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
