From owner-freebsd-questions Tue Dec 5 23:37:52 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA20521 for questions-outgoing; Tue, 5 Dec 1995 23:37:52 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA20494 for ; Tue, 5 Dec 1995 23:37:48 -0800 (PST) Received: from sasami.jurai.net (root@sasami.jurai.net [205.218.122.51]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id XAA27667 for ; Tue, 5 Dec 1995 23:09:51 -0800 Received: (from winter@localhost) by sasami.jurai.net (8.6.11/8.6.9) id BAA03059; Wed, 6 Dec 1995 01:09:42 -0600 Date: Wed, 6 Dec 1995 01:09:42 -0600 (CST) From: "Matthew N. Dodd" X-Sender: winter@sasami To: freebsd-questions@freebsd.org Subject: Re: Processes -will- -not- die! In-Reply-To: <199512050112.UAA12000@j51.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk On Mon, 4 Dec 1995, Drew Morone wrote: > 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. I have also seen this problem. One case where dialup shell users get cut off while running pine and the other where local XTerm users close the xterm w/o exiting Pine. Both result in pine hanging in a cpu-eating loop. Annoying but doesn't really hurt much. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"|