Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!ACC.FLINT.UMICH.EDU!jal
From: jal@ACC.FLINT.UMICH.EDU (John Lauro)
Newsgroups: comp.sys.apollo
Subject: Re:  /dev/null
Message-ID: <AA04189@acc.flint.umich.edu>
Date: 22 Apr 91 19:16:56 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 9


	Does anyone know why is /dev/null (the prosess) eating so much cpu?
	Does everybody use it so much....:)

null is used when the node has nothing else to do.
What I dislike, is it's also used if the reason the node has nothing
else to do is because it's constantly waiting for disk I/O because
there is too little memory.  (An overworked node will actually show
small uptimes... as in 0.01.  That can be extremely missleading)