i installed fc3 1 week ago and since some weired things are happening. out of nowhere the hdd starts going off like crazy, the cpu runs at 100%, the temperature goes up. all these are caused by "makewhatis". witch i don't know how it started and why. and worst of all is that i can't kill it! anybody had experience this?
Am So, den 01.05.2005 schrieb sly um 17:58:
i installed fc3 1 week ago and since some weired things are happening. out of nowhere the hdd starts going off like crazy, the cpu runs at 100%, the temperature goes up. all these are caused by "makewhatis". witch i don't know how it started and why. and worst of all is that i can't kill it! anybody had experience this?
sly
less /etc/cron.daily/00-makewhatis.cron man makewhatis
Alexander
On Sun, 1 May 2005, sly wrote:
i installed fc3 1 week ago and since some weired things are happening. out of nowhere the hdd starts going off like crazy, the cpu runs at 100%, the temperature goes up. all these are caused by "makewhatis". witch i don't know how it started and why. and worst of all is that i can't kill it! anybody had experience this?
It's part of regular daily system maintenance. makewhatis creates a database of summaries of man pages to answer queries like "man -k", "apropos", and "whatis". It's fairly disk-intensive, but shouldn't take more than a few minutes.
The other disk-intensive daily operation is updatedb, which builds the database for "locate". That command lists paths to all files where the path containts a particular string. It's much faster than "find", but requires an up-to-date database. Again, it shouldn't take more than a few minutes each day.
You can shut these off if you want by removing scripts in /etc/cron.daily, but you will find that the usefulness of the commands these databases support will decay over time--if you don't run updatedb regularly, you won't be able to "locate" files added since the last updatedb, and if you don't run makewhatis, you won't be able to "apropos" man pages added after the last makewhatis.
sly wrote:
i installed fc3 1 week ago and since some weired things are happening. out of nowhere the hdd starts going off like crazy, the cpu runs at 100%, the temperature goes up. all these are caused by "makewhatis". witch i don't know how it started and why. and worst of all is that i can't kill it! anybody had experience this?
I have to give a seminar using OO.o Impress / FC3, in a Dell Inspiron 8600 laptop. I wonder if anyone could give me a hint on how to make it work with a projector.
Prelink also hogs the CPU and causes a similar problem as you describe. Rather than disable all of these services, adding preference entries for controlling background processes to run at lower percntages would be a better approach.
A twenty to thirty degree temperature rise caused by a background process bogging down the processor is a bad approach for background processes. Having processes disabled that are useful is not the answer either.
Jim
On Sun, May 01, 2005 at 03:45:02PM -0400, Jim Cornette wrote:
Prelink also hogs the CPU and causes a similar problem as you describe. Rather than disable all of these services, adding preference entries for controlling background processes to run at lower percntages would be a better approach.
They *do* run at lowered priority, but maybe also doing something to limit their CPU usage would also be good.
Matthew Miller wrote:
On Sun, May 01, 2005 at 03:45:02PM -0400, Jim Cornette wrote:
Prelink also hogs the CPU and causes a similar problem as you describe. Rather than disable all of these services, adding preference entries for controlling background processes to run at lower percntages would be a better approach.
They *do* run at lowered priority, but maybe also doing something to limit their CPU usage would also be good.
I'm for this since programs like cpufreq do what they are supposed to do, they up the processor speed when the CPU load rises. Since this is a background process, I could care less if the program took twice the time to complete. I would not be aware of it running if it did not produce higher temperatures or reduced responsiveness since it cannot hog the processor.
Hopefully this can be worked out for laptop users as well as for computers that are not left on 24/7.
Jim
-
Alexander Dalloz -
Jim Cornette -
Matthew Miller -
Matthew Saltzman -
sly