Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!news.uoknor.edu!news.ecn.uoknor.edu!paladin.american.edu!howland.reston.ans.net!nctuccca.edu.tw!news.cc.nctu.edu.tw!news.sinica!taob
From: taob@gate.sinica.edu.tw (Brian Tao)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Zombie processes eating up CPU time (was Re: Internet Service Provider)
Date: 27 May 1995 05:58:42 GMT
Organization: Institute of Biomedical Sciences, Academia Sinica
Lines: 13
Distribution: best
Message-ID: <3q6f2i$nl0@gate.sinica.edu.tw>
References: <3pqb92$lq2@pt9201.ped.pto.ford.com> <D941A5.659@twwells.com> <3q2k6c$lvn@NNTP.MsState.Edu> <3q340c$kqc@shell1.best.com>
NNTP-Posting-Host: @140.109.40.249
In article <3q340c$kqc@shell1.best.com>, Matt Dillon <dillon@best.com> wrote:
>
> Well, I would say that setting a general CPU limit is not really a good
> solution... it will break valid programs worse then it will fix broken
> ones.
I'm not suggesting that the limit be imposed on every process, nor
that it is a valid solution for all situations. It does work quite
nicely in an ISP user environment, and at worst gives you some extra
time to work on kernel or client fixes.
--
Brian ("Though this be madness, yet there is method in't") Tao
taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org