From owner-freebsd-questions Tue Jan 7 05:12:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA21506 for questions-outgoing; Tue, 7 Jan 1997 05:12:57 -0800 (PST) Received: from revelstone.jvm.com (revelstone.jvm.com [207.98.213.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA21501 for ; Tue, 7 Jan 1997 05:12:54 -0800 (PST) Received: (from fbsdlist@localhost) by revelstone.jvm.com (8.7.5/8.6.12) id IAA01024; Tue, 7 Jan 1997 08:12:53 -0500 (EST) Date: Tue, 7 Jan 1997 08:12:53 -0500 (EST) From: Cliff Addy To: freebsd-questions@FreeBSD.ORG Subject: Pine running wild Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Every so often, I'll notice our server is working harder than usual. I'll log in and find a copy of pine consuming 80-90% of the cpu time. If not caught, it will go on like this for hours. The user is not logged in, it may be caused when a user loses their intetnet connection. However, I lose my connection all the time in pine and it never happens. In fact, 95% of the time, it's the same user. 1) Why would this be isolated to a single user? What's the real underlying cause? 2) I'm thinking of writing a perl script to spot and kill these processes. However, how would I identify them? Probably at any given moment, a non-running-amok pine would use 80-90% of the cpu, perhaps I could track that pine over 5-10 seconds and kill ones that continue at this rate? Cliff