home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!caen!hellgate.utah.edu!cc.usu.edu!ivie
- From: ivie@cc.usu.edu (CP/M lives!)
- Newsgroups: comp.arch
- Subject: Re: Interrupts vs Polling---WAS: cooling
- Message-ID: <1992Aug27.114905.58435@cc.usu.edu>
- Date: 27 Aug 92 11:49:05 MDT
- References: <BtED7C.5II@exnet.co.uk> <BtEy50.Ix4.2@cs.cmu.edu> <BtIDsH.8x3@exnet.co.uk> <BtMC8n.B6H.2@cs.cmu.edu>
- Organization: Utah State University
- Lines: 13
-
- In article <BtMC8n.B6H.2@cs.cmu.edu>, lindsay+@cs.cmu.edu (Donald Lindsay) writes:
- > It *is* sometimes important to get fast notice of cooling failure.
- > Some systems, stopped abruptly, get hot enough to damage themselves.
- > Their power-fail sequence tries to have residual power, not for the
- > CPU or disks, but for the fans/pumps.
-
- While I hate to inject folklore into comp.arch, the local university
- had a power failure a while ago. While all the machines kept running on
- the UPS, the air conditioner for the machine room did not (it had been
- left off the UPS), so they had to shut down.
-
- Roger Ivie
- ivie@cc.usu.edu
-