From owner-freebsd-stable Wed May 8 19:34:51 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA27476 for stable-outgoing; Wed, 8 May 1996 19:34:51 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA27464 for ; Wed, 8 May 1996 19:34:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id TAA01240; Wed, 8 May 1996 19:34:27 -0700 (PDT) Message-Id: <199605090234.TAA01240@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: Scanner SOD cc: freebsd-stable@FreeBSD.org Subject: Re: pine In-reply-to: Your message of "Wed, 08 May 1996 20:37:46 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 08 May 1996 19:34:27 -0700 Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >Ive noticed that in my new sup of -stable that the pine application has a >tendency to runaway and cause the following run away process: > >5388 lucid 105 4 1232K 1452K run 365:17 96.02% 96.02% pine > >I know its happens in any unix but its happening with increased frequency >in -stable from my -release system. > Not a major thing I was just curious if anyone could explain why. >Im more curious than anything. And if there was a way to fix it, a patch >or something? It's only a coincidence that it is happening more frequently under -stable. This bug in pine is believed to be caused by improper handling of the tty after it is abnormally closed (not handling the EOF on reads), but as far as I'm aware, noone has yet to actually prove this to be true. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project