On 7/29/05, T. Horsnell <tsh(a)mrc-lmb.cam.ac.uk> wrote:
>Hi list,
>Once again my FC4 box (Duron 1200mHz, 512 ram) has crawled to a halt.
>I quickly top'ed and found a process prelink that varied between
>74%-98% CPU usage.
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 5202 root 39 19 11724 9280 536 R 89.9 1.9 0:23.59 prelink
>
>So I googled for prelink and now know that it helps preload libraries
>so that progreams can start faster. Which is senseable because the
>machine started slowing down when I clicked 'manage bookmarks' in
>firefox, which opens another program. My question is, what can I do to
>prevent this from happening again? Do I have to ust cross my fingers
>every time I open a new program?
>
If you look in /etc/crontab, you will probably see something like:
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# run-parts
01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly
This tells cron to run stuff at regular intervals.
If you look in /etc/cron.daily/ you will see things like
00-logwatch
00-makewhatis.cron
0anacron
logrotate
prelink
rpm
slocate.cron
tetex.cron
tmpwatch
yum.cron
Looking at the prelink script, it goes round your system seeing if
there is any new stuff to prelink.
Likewise 00-makewhatis.cron re-builds the 'whatis' database
These are both disk-intensive (hence cache-consuming)
things which you may not want to do so frequently...
Cheers,
Terry.
Thanks, I may just turn down the frequency of those things.
Dotan Cohen
http://song-lirics.com/sl/artist/321/madonna-lirics.php
Dotan Cohen