Question: why does TC wake up a spun-down hard drive on the first instance of some programs (like Apps for instance) with all of my extensions loaded as "onboot" ?
Setup: I use TC 9.0 burned to a usb stick as my boot device only. I keep my data on the hard drive /dev/sda/tce. No problems. Tc finds and uses it.
For long runs of TC, or for machines that won't function properly without a working hard drive, I'll spin the platter down:
sudo hdparm -y /dev/sda
Rather than put my ear to the case to check for activity, I'll use this to garner the status:
sudo hdparm -C /dev/sda
Fine. I'm just wondering why when the drive has been successfully spun down, most of the utility programs won't spin up the drive, but a program like Apps will on their first run? But things like Editor, Run, etc won't?
Interestingly enough, if the Apps program for example spins up the drive on it's first run, and I issue a successive hdparm spindown, if Apps is run again, then the drive stays spun down. This behavior is repeatable with my own tcz's, like HTOP, etc - which were run as "onboot". First run spins up the drive. Second runs *after* another hdparm spindown stay spundown.
'kinda puts a damper on my hdparm spindowns, as I may inadvertently spin it up again on a program's first run.
I'm thinking that the programs are looking for config files or extra data to load - despite being designated as onboot. Hmmm interesting.