You're true in all points. I could clarify one thing more : the disk with home and var and usr and / and all system points is a SSD so always running.
I have mounted two separately drives which are both high capacity classic rotating hard drives. The daily script wakes them up and I would like to avoid this because sometimes it really is not necessary to run the disks for some time and it is useless to simply wake and asleep them each day. They are only data disks mounted in /mnt TY Le samedi 17 octobre 2009 C 12:01 +0200, Paul de Weerd a C)crit : > On Sat, Oct 17, 2009 at 11:49:01AM +0200, jean-francois wrote: > | Hello, > | > | Each time the daily script is run, the two hard disks are woken-up - I > | could not yet clearly identify wich line of code actually wakes them up > | - does someone know this ? > > Ehr, not sure what you mean. When you try to access the disk, of > course it wakes up (if asleep). How else are you going to read data of > them ? If your question is about what part of the daily script touches > the disk, then I think the answer is 'just about all parts'. Remember > that the script itself and all the programs it runs during execution > are stored on disk. > > If you don't want to run the daily script (to avoid waking your > disks), disable the cronjob that runs them. If you want to shoot > yourself in the foot, the gun is right there. > > Cheers, > > Paul 'WEiRD' de Weerd
