Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
ive turned off all syslog activity (i think) only thing i know of for sure thats still llogging is acpid. gets a batt signal every single minute i think its something to do with ac power being plugged in. i dont know how to stop acpi from logging. any help?
A couple of things can cause activity like this. One would be insufficient RAM, which leads to disk thrashing. Another would be the "updatedb" program which keeps an index or database of information on locations of all files for the "locate" command. I have found the latter to be fairly common on my system.
ok ive stopped acpid logging by sending its output to /dev/null. ive stopped each of the running processes and all syslog, kernel log, and i still have this problem. its like every 20 seconds or so theres just a little tick on the hard drive when im watching gkrellm. how can i find out what is going on there? i really need to stop this ghastly activity so my hard drive can turn off once in awhile.
im not positive but it seems that it may have some relation to similar activity on eth0: tick on eth0, tick on hda............tick on eth0,tick on hda.......... like that. but i turned off all the network services and it was still doing it on the hard drive
I've experienced this happening to drives shortly before they die.. Its actually happening to one of my drives (IBM, SCSI, DDYS-) right now! And it had previously happened to this same drive shortly before I had RMAed it for the second time due to failing. Unfortunately, I can't RMA the drive until it gives a fail code with their test utilities.
It has to be said... are you sure you want your HDDs to spin down? It is my understanding that when they spin, they basically float on acushion of air, with no metal touching metal, and the wear is basically nil when spinning. I was lead to believe the stress and wear to a HD is spinning up and spinning down.
Sorry for going off-topic a bit, and I'm sure you have a good reason for wanting to spin down, but I'm just keying this in because of my belief that it's better to have a disc always spinning than continually stopping and re-starting.