From owner-freebsd-isp Fri May 31 01:30:40 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA28593 for isp-outgoing; Fri, 31 May 1996 01:30:40 -0700 (PDT) Received: from marikit.iphil.net (map@marikit.iphil.net [203.176.0.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA28582 for ; Fri, 31 May 1996 01:30:32 -0700 (PDT) Received: (from map@localhost) by marikit.iphil.net (8.7.5/8.6.9) id QAA07394; Fri, 31 May 1996 16:29:29 +0800 From: "Miguel A.L. Paraz" Message-Id: <199605310829.QAA07394@marikit.iphil.net> Subject: Re: detecting and killing CPU hogs To: angio@aros.net (Dave Andersen) Date: Fri, 31 May 1996 16:29:28 +0800 (GMT+0800) Cc: freebsd-isp@freebsd.org In-Reply-To: <199605310819.CAA31977@terra.aros.net> from "Dave Andersen" at May 31, 96 02:19:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dave Andersen wrote: > My suggestion is a quick perl script to do it that parses the output of > a ps -auxw. If you want, I can send you the one I use here, but you'll > probably want to customize it for your own system. 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. > The other option is to have the users shells execute a 'limit' when > they log on. :-) I haven't tried that approach, as a decision was made > to use bash as the default shell here. Same here! It's not my system, but a client's, actually. Any users out there particularly fond of csh? -- miguel a.l. paraz iphil communications, makati city, tech problems, to philippines.