From owner-freebsd-questions Mon Dec 4 17:54:38 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA20229 for questions-outgoing; Mon, 4 Dec 1995 17:54:38 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA20219 for ; Mon, 4 Dec 1995 17:54:35 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id RAA06193; Mon, 4 Dec 1995 17:54:32 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id RAA06084; Mon, 4 Dec 1995 17:54:50 -0800 Message-Id: <199512050154.RAA06084@corbin.Root.COM> To: Drew Morone cc: freebsd-questions@freebsd.org Subject: Re: Processes -will- -not- die! In-reply-to: Your message of "Mon, 04 Dec 95 20:12:03 EST." <199512050112.UAA12000@j51.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 04 Dec 1995 17:54:50 -0800 Sender: owner-questions@freebsd.org Precedence: bulk >For some reason, some of the user apps on my system will get hung, and >won't die when somebody exits unceremoniously. I of course have to go in >and kill the process, which proceeds to suck up all of the CPU. This >seems to happen most with "pine" and "tin", but will happen with other >software as well. This is caused by 'pine' and 'tin' not handling the EIO return from a read properly. When the TTY gets disconnected, input from stdin loops continuously while ignoring the error return. (I might have this backward - it might be on the output side or both). -DG