Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have configured noflushd to spin down the hard disk after a period of inactivity, but it spins right up again after a minute or two (sometimes less). Something is accessing the disk periodically -- I can see it happening in KDE System Guard. I have disabled almost all logging, so I don't think that's the problem. How do I find out what's doing this?
There are lots of proesses running, but none of them tells me exactly when it's accessing the disk. In KDE I can look at the status of each one (running, sleeping, etc.) but this hasn't seemed to help.
(The list of running processes is too long and boring to reproduce here.)
As soon as you see that 'something' is accessing your hard disk, open a terminal immediately and give the command:
top
This command will show the processes running in the background at real time. You can kill the specific process that you may want and check which is the 'offending' process.
Even I have the same issue, when suddenly 'something' starts accessing my hard disk.....But in my case, that command was the 'updatedb' command.....
When you issue the 'top' command, check the column with heading 'N' ...... This will show the priority with which the process is running...
The Lowest priority is -20
and highest is 19
that means, if the process is running suddenly, it will have a high 'nice priority level'.
Just check for the process on top of the running processes list, that has the highest priority number ( in my case updatedb was running with priority 19)
Thanks for the help. The disk access is only for one or two seconds, so it's not enough time for me to open the console and get top running, but I'll leave a console open with top running and see how that works (it seems to refresh itself every couple of seconds).
Mandrake has a "services" GUI front end that lets you review which daemons are set up to run (in the rc system). If your distro has the equivalent, read through them, and (after researching!) disable the ones that aren't necessary.
Also review your cron folders, and see what is being periodically run, and if you can either reduce the frequency or remove them completely.
One potential disk churner is slocated, which is akin to Microsoft's Find Fast. It is often set up to run daily, but really most people can get by with running it weekly.
If you're running a desktop, you can remove most of the server daemons (there are a few exceptions, however.)
Thanks for the tips. slocated does run on my system, once daily. cron seems OK (just my backup).
I'm running Debian, but I'm sure there's an equivalent "services" type feature. I can see which daemons are running in KDE, and I can kill them, but I'm not sure how to specify which ones are loaded at startup. More research...
Also: I've been watching "top" in the console, and it seems like the KDE services are the ones with the highest priority. And when I get my little two-second disk hit, nothing on the list changes.
Hm, I wonder whether it is KDE itself (perhaps causing a dip into disk based memory?) I had horrendous performance on my PC running KDE. Try running one of the lighter frontends - IceWM or Blackbox - and see if the same thing happens. You can with a little tweaking get either of those window managers to give you all of the niceties of KDE without the heavy resource load. (I recommend plugging Rox Filer into them).
Yes, I think you're right: KDE is always at the top of "top", with these services:
XFree 86
kdeinit
kmail
keventd
ksoftirq_CPU0
(plus a few others lower down).
I'm not familiar with other window systems, but I'll check them out. Also, I'll try to boot into "Expert mode" (it's one of the options that LILO gives me on my Xandros bootup) which does not load KDE, and will see if the problem persists without KDE running.
Where would I find out about the "tweaking" I'd need to do with the other window systems?
If you go with IceWM, download the Ice Windows Control Panel. That'll do 95% of what you need to customize it. Blackbox or (other) will have similar configuration utilities.
XFree86 is XWindows, which is the basis for graphical linux systems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.