From owner-freebsd-isp Fri May 31 08:52:12 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA20215 for isp-outgoing; Fri, 31 May 1996 08:52:12 -0700 (PDT) Received: from mail.calweb.com (mail.calweb.com [165.90.138.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA20210 for ; Fri, 31 May 1996 08:52:09 -0700 (PDT) Received: from devnull.calweb.com (devnull.calweb.com [165.90.138.92]) by mail.calweb.com (8.7.5/8.7.3) with SMTP id IAA06813; Fri, 31 May 1996 08:51:37 -0700 (PDT) Message-Id: <2.2.32.19960531155146.0071577c@jpop.calweb.com> X-Sender: jfesler@jpop.calweb.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 31 May 1996 08:51:46 -0700 To: "Miguel A.L. Paraz" From: Jason Fesler Subject: Re: detecting and killing CPU hogs Cc: freebsd-isp@freebsd.org Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 03:27 PM 5/31/96 +0800, you wrote: >Hi! > >Is there a way to do kill programs like this via scripts: > >> 1989 p0- RN 1688:47.17 lynx >> 7488 p0- RN 1477:42.69 lynx >> 15296 p0- RN 5359:54.88 lynx >> 17227 p0- RN 2380:00.85 lynx >> 19982 p1- RN 429:47.18 pine >> 21068 p1- RN 419:02.95 pine I nearly did so, but found too many problems with killing the wrong ones :-). People get upset about that ;-) Everyone who works here, though, has the current network and load status built into their prompt (ala tcsh's magic). Any time something goes down, or the load gets high, they know about it. I *do* kill off "guest" entries where the CPU is high - guesst will never load pine, tin, etc [which spike the CPU usage for their processes pretty easily]. >I think these are caused by people who run these from the shell via >a telnet session, which gets disconnected. Am I right? Bingo. -- Jason Fesler jfesler@calweb.com Admin, CalWeb Internet Services jfroot@calweb.com I like my Usenet over ice, please. http://www.gigo.com Disclaimer: My /dev/null can beat your /dev/null any day.