I've had mixed results, and I'm still not up to speed on
this -- however:
When I tapped Fn+Standby on my Dell Latitude 450 MC,
initially the machine would 'bounce back' in about half
a second -- it would look like it was going to go to
sleep, and then it'd come right back. Eventually, I
disabled gpm (for the mouse) and that seemed to do the
trick. I was half-convinced that's all I need do, since
the logs clearly showed that 'nothing happened' for
several hours, and 'cron.daily' did not run at the
appointed hour. It ran as soon as I opened the closed
cover of the 450 MC! (within a few minutes of that,
I need to read more, and find out what programs or
daemons would help me, but the suspend (Standby) function
of the BIOS seems to work pretty well on it's own. I
wish I'd taken better notes, because I tried this earlier
in the year, and could not make it work at all. The
only things I've done to help were to add 'apm=on' to
the lilo.conf (or the ms-dos batch file that calls
loadlin) and that business about gpm.
--- In email@example.com
, "Ned Ragdnuos"
> david epstein <dba-@...> wrote:
> > Is there any way of controlling the length of time the disk spins
> > before it stops? I have an Inspiron 7000, but I don't suppose it
> > matters. I think such things are under user control in Windows.
> > I have a related problem using apm -S. Sometimes the machine shuts
> > down briefly after I type apm -S as root. But then it starts up
> > as though some event has woken the machine up. When it is in such
> > mood, it seems just about impossible to get apm -S to work. I
> > that if I could stop the disk spinning first, then apm -S would
> > David Epstein
> I used
> # hdparm /dev/hda -S 1200
> but there's just too many processes and stuff doing 'sync'
> at the moment so the disk keeps spinning back up.
> If I kill off most of the daemons and don't run too much stuff,
> the disk can stay asleep for about 5 minutes.