Date: Fri, 31 May 1996 02:35:33 -0600 (MDT) From: Dave Andersen <angio@aros.net> To: map@iphil.net (Miguel A.L. Paraz) Cc: angio@aros.net, freebsd-isp@freebsd.org Subject: Re: detecting and killing CPU hogs Message-ID: <199605310835.CAA32523@terra.aros.net> In-Reply-To: <199605310829.QAA07394@marikit.iphil.net> from "Miguel A.L. Paraz" at May 31, 96 04:29:28 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Lo and behold, Miguel A.L. Paraz once said:
> I can do it... I just need to know the criterion for telling which
> processes should be killed... those whose owners aren't logged in?
> But then, it could be a POP daemon or something similar.
I do it by the amount of time the process has used up. I have two
categories for programs depending on how much time I think they should
be allowed to eat. I only kill certain processes - elm, pine, tin, lynx,
bash, etc., that seem to go wild. So then just see if:
o They're not root
o It's not a process you really don't want killed. (init comes to
mind). Perhaps excessive paranoia, but with something that
kill -9's as root, I tend to prefer it. :)
o The process is on your kill list
o The process has used > XX minutes of CPU time.
> Same here! It's not my system, but a client's, actually.
> Any users out there particularly fond of csh?
I use tcsh. Great shell, especially if you're an emacs kind of person.
-Dave Andersen
--
angio@aros.net Complete virtual hosting and business-oriented
system administration Internet services. (WWW, FTP, email)
http://www.aros.net/ http://www.aros.net/about/virtual
"There are only two industries that refer to thier customers as 'users'."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605310835.CAA32523>