Re: OSALoad/OSACompile block when machine is asleep
Re: OSALoad/OSACompile block when machine is asleep
- Subject: Re: OSALoad/OSACompile block when machine is asleep
- From: Markus Hitter <email@hidden>
- Date: Wed, 14 Nov 2001 12:38:13 +0100
Am Mittwoch den, 14. November 2001, um 03:13, schrieb Brant Vasilieff:
I guess I mean idle, or possible doze. I'm not sure.
"idle" is when all is running but no process is actually using
the processor. "Doze" is some mode where the processor sleeps
for fractions of a second. Not visible to the normal user. Well,
I'm only 99% sure, too.
Any file read with a cache miss should spin up the disk.
I'm not seeing this. I tried reading a file, but was worried
about the second time around having it in the cache, so I tried
writing a small file as well. What happens, is that the file
is created, but not actually saved to disk until I move the
mouse and wake up the machine. The creation date matches the
time I attempt to save it, but the modification date is set to
the time when the drive actually spins up.
To produce cache misses, you can hide physical RAM with the
nvram variable "ram-size", see "man nvram"
Other way is to read/write a really big file.
But in no way an executing script should be blocked by a stopped
disk. I'd call this a bug.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/