huh?

[David A. Bandel]

On Wed, 20 Mar 2002 11:12:23 -0700
begin  Myles Green <mylesg at telusplanet.net> spewed forth:

> On Wed, 20 Mar 2002 07:27:47 -0500
> "David A. Bandel" <david at pananix.com> wrote:
> 
> > On Tue, 19 Mar 2002 23:41:27 -0700
> > begin  Myles Green <mylesg at telusplanet.net> spewed forth:
> > 
> > > I came home this evening to find my web server powered down with the
> > > following entries in /var/log/messages:
> > > 
> > > Mar 19 12:00:59 a0gz395zy10de kernel: usb.c: USB disconnect on
> > > device 125 Mar 19 12:00:59 a0gz395zy10de kernel: hub.c: USB new
> > > device connect on bus1/1, assigned device number 127 Mar 19 12:01:01
> > > a0gz395zy10de dhcpcd[8690]: terminating on signal 15 Mar 19 12:01:02
> > > a0gz395zy10de network: Shutting down interface eth0:  succeeded Mar
> > > 19 12:01:02 a0gz395zy10de apmd[9160]: System Suspend
> > 
> > apmd[9160]: System Suspend
> > 
> > Your power saver daemon suspended your system.  If you don't want
> > that: killall apmd
> > rmmod apm
> 
> Thanks David. I don't quite understand why apmd would shut down a system
> that was under a fairly heavy load and has (make that had) been up for
> 60 days.
> 

I suspect if you look in your BIOS setup you'll find the reason.  Check to
see which events might act as a wakeup beyond keyboard or mouse usage. 
Turn on any that should prevent a system suspend (like disk activity,
network activity, etc.).  But if you don't need it, don't run apmd or the
apm module.

Ciao,

David A. Bandel
-- 
Focus on the dream, not the competition.
		-- Nemesis Racing Team motto
Internet (H323) phone: 206.28.187.30