From owner-freebsd-stable Wed Apr 8 09:09:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28181 for freebsd-stable-outgoing; Wed, 8 Apr 1998 09:09:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA28156 for ; Wed, 8 Apr 1998 09:09:37 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yMxPo-0003Hk-00; Wed, 8 Apr 1998 09:09:32 -0700 Date: Wed, 8 Apr 1998 09:09:31 -0700 (PDT) From: Tom To: Eddie Irvine cc: freebsd-stable@FreeBSD.ORG Subject: Re: A new Bug with FreeBSD? In-Reply-To: <01bd62c8$0905d3c0$a01a1acb@gretchen> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, 8 Apr 1998, Eddie Irvine wrote: > top should show the "ee" process still active, > using up 95% of CPU time. Now go to your > ethernet hub. It should show a whole heap > of activity - much more than normal. > > I presume this shouldn't happen on a Unix system - > all processes should be children of the logged in > user, and thus should get KILL'ed when the user > exits, no matter how they exit. No, this is an application bug. Applications are sent a HUP signal, which they could ignore. Then the application stupidly gets in a tight-loop reading from a non-existant connection. I normally would set a CPU time limit so broken applications like ee don't last that long. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message