On Mar 18, 2004, at 14:03, Thomas Lamy wrote:
turgut kalfaoglu schrieb:
Well, even after I disable urandom, which my system does not have anyway,any output from "truss -p <pid>" where <pid> is the process id of the cpu eating clamd ?
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.
help!
-turgut
The problem with ktrace or truss is that you often are looking at library calls and they may look like similar calls in the source. That fooled me for quite a few days. The poll call was not the one in the clamd source. Spent a lot of time trying to figure out how a constant got changed to zero only when poll was called. Turned out the poll was in the read library. Walking through the code with gdb is more effective, but takes a lot more time and really disrupts the system performance.
------------------------------------------------------- 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
