On Thu, 13 Oct 2005, Tony Nelson wrote:
At 9:43 AM -0400 10/13/05, Matthew Saltzman wrote:
...
I wonder if nicing it would avoid the problem of making your machine
unresponsive. I don't see why it has to run at regular priority.
I see a renice +19 in /etc/cron.daily/prelink. Of course, this won't
Oops, missed that when I glanced at it.
reduce the CPU usage below 100%, it just changes who gets it first.
So it shouldn't make a system unusable in any case (unless maybe the
system is memory constrained and swapping along with everything else).
Also, the amount of work prelink does can be controlled in
/etc/sysconfig/prelink. Normally, it should be quick (only bins and libs
that have changed), but every two weeks it runs normally. If you aren't
upgrading RPMs, it apparently doesn't do anything at all until after a
week elapses.
...
Anything that confuses prelink enough that it always runs a full prelink
would make it take a long time. Perhaps it can't find /etc/prelink.cache
or it thinks the cache is bad or some such. Perhaps -v would help diagnose
the problem, as would running it directly and observing.
And (disregarding philosophical objections to prelink "munging" binaries)
would seen to be the most utilitarian approach to solving the problem.
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
