im running the website off solar power so efficiency is the name of the game..
Ive configured hdparm and noflushd to powerdown the drive after a few minutes. I have all my logs starting with a -so as not to cause a diskwrite as suggested, cron is cleaned out. all i can see is the suse firewall logging stuff constantly.. not really errors just status.. (in the messages log).
this is a machine thats a webserver but its a quiet site and often hours go by with no visits.. im not really sure the drive is being shutdown. anybody know how to limit/adjust the suse firewall logs and/or any other items i can do to see whats going on?
heres the commands i start each with im not sure if perhaps they conflict w/each other as they both have a spindown time..

hdparm -c3 -m8 -M0 -S80 /dev/hda
noflushd -n 6 /dev/hda

tia!

hi everyone, i just found the oddest, most disapointing thing, hopefully some of you have more feedback. after trying some of the things ive found on the site here (running top - cool, or ps aux) and reading about people seeing kde as using lots of resources i decided to startup with windowmanager as its already installed.

for the first time i just heard the hardrive shut down while i was web browsing!! this is great, and bad. windowmanager is very slick and seems to display quicker, and I certainly have less processes running now. but it';d be nice to switch over to kde if i choose.. but if its going to keep the disk spinning and processor busy while it does nothing i will have to look elsewhere, thats completely unacceptable. any tips for killing processes in kde or is that just how it goes??