*BSD News Article 44722


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!gatech!swrinde!emory!nntp.msstate.edu!Rain.MsState.EDU!not-for-mail
From: stormy@Rain.MsState.EDU (Stormy Henderson)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Zombie processes eating up CPU time (was Re: Internet Service Provider)
Date: 25 May 1995 19:01:32 GMT
Organization: Stormy's Bar & Grill
Lines: 42
Message-ID: <3q2k6c$lvn@NNTP.MsState.Edu>
References: <3pqb92$lq2@pt9201.ped.pto.ford.com> <3prh5v$au8@fnord.dfw.net> <D91uu8.7J3@twwells.com> <3pub0e$ppd@gate.sinica.edu.tw> <D941A5.659@twwells.com>
Reply-To: Stormy@GTLUG.ORG
NNTP-Posting-Host: port26.ts2.msstate.edu
X-Newsreader: TIN [UNIX 1.3 941216BETA PL0]

T. William Wells (bill@twwells.com) writes...

   : frenzy looking  for input  data.  The  incessant looping  drives the
   : program  to hog  almost  all  the CPU,  to  the  detriment of  other
   : interactive programs.

   Like, duh. I know all this.

   :     Our solution: give every user a CPU quota.

   *You*  give every  user a  CPU quota. *I*  am not  in the  business of
   putting  limits on  my customers  just  because I  am using  defective
   software.

   :                                                  See the man page on
   : csh/tcsh for  the built-in  "limit" command, and  the man  pages for
   : getrlimit(2) and setrlimit(2).

   Do you know  how fatuous you sound  to a guy who  has been programming
   and administering Unix systems for twelve years?

   Please don't  waste my time with  the obvious. This is a  problem that
   needs  to be  *fixed*, by  fixing the  OS, not  by piecemeal  hacks on
   applications, or bandaids added to the various shells.

Just because  you find it  obvious,  doesn't  mean that everyone  else does. 
Besides, the obvious is overlooked frequently.                              

Not everyone  has been adminstrating un*x  systems for twelve years  and has
the knowledge of how  to solve a problem that has  been plaguing many users.
This person posted  a general work-around for the problem,  which is quite a
reasonable one (the  solution, not the problem), and will  definitely do the
job.  If it's not a solution you can use, just ignore it, rather than making
a jerk of yourself  in public by flaming him for  trying (and succeeding) at
being helpful.

Be nice to each other...
         
                     ------------------------------------
                     ---- Stormy Sebastian Henderson ----
                     --------- Stormy@Gtlug.ORG ---------
                     ------------------------------------