At 9:13 PM +0300 7/29/05, Dotan Cohen wrote: >On 7/29/05, Tony Nelson <tonynelson@xxxxxxxxxxxxxxxxx> wrote: >> I don't think this is a a swap problem. If it were, the process would be >> out of memory, but instead it's using little memory but lots of CPU. >> Prelink is supposed to be disk intensive, not CPU intensive, so maybe it's >> a bug in prelink or something it uses. >> ____________________________________________________________________ >> TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> >> ' <http://www.georgeanelson.com/> >> > >Really? Where would I begin to debug? In what logs should I start poking >around? I wouldn't expect it to be logging anything (though I might be wrong -- do you have any suddenly huge log files?). I think it's probably just stuck in a loop ("hung"). In that case, the correct tool would be gdb, but it would take lots of handholding (from someone with more experience than I) for you to make that useful. One thing to look for is whether prelink is always running, even after you kill it or reboot or whatever. Anything using 85% of the CPU will make everything else slow. If you haven't run prelink for a long time maybe it just has a lot to do. But I really expect that it would spend most of its time reading files, and then writing them back out, not calculating stuff. ____________________________________________________________________ TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' <http://www.georgeanelson.com/>
