From owner-freebsd-questions  Wed Aug  7 15:42:14 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA14908
          for questions-outgoing; Wed, 7 Aug 1996 15:42:14 -0700 (PDT)
Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA14901
          for <questions@freebsd.org>; Wed, 7 Aug 1996 15:42:12 -0700 (PDT)
Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net
           id ae00870; 7 Aug 96 23:42 +0100
Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net
          id aa19353; 7 Aug 96 23:37 +0100
Received: (from fqueries@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id SAA02538; Wed, 7 Aug 1996 18:09:06 GMT
From: James Raynard <fqueries@jraynard.demon.co.uk>
Message-Id: <199608071809.SAA02538@jraynard.demon.co.uk>
Subject: Re: Pine maxes host out...
To: John Clark <jc@netview.net>
Date: Wed, 7 Aug 1996 18:09:06 +0000 ()
Cc: questions@freebsd.org
In-Reply-To: <2.2.32.19960806155116.009983a8@netview.net> from "John Clark" at Aug 6, 96 03:50:26 pm
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I have an occasional problem with pine under FreeBSD 2.1-RELEASE.  See how
> this process (below) becomes detached from the user and eats CPU time like
> nobody's business?
> 
>  USER       PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED       TIME COMMAND
>  username   143 126.9 10.5  3160 3248  p0- RN    1:12PM   34:00.91 pine
> 
> I can kill -9 the process ok, and things return to normal... it is just that
> sometimes this goes on for hours before I get to it, yielding .99 (or so)
> utilization in the mean time.
> 
> Does anyone know why this is, or what can be done about it?  

Probably a bug in pine sending it into an infinite loop.  It's useful 
to leave something like top or xperfmon++ (both in the ports) running 
and glance at them occasionally, so you can see if any programs are
hogging the CPU.  (Careful though - xperfmon++ has a memory leak and
will become amazingly bloated if you don't stop and restart it every
now and again).