From owner-freebsd-hackers Sun Sep 28 15:59:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28580 for hackers-outgoing; Sun, 28 Sep 1997 15:59:46 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28572 for ; Sun, 28 Sep 1997 15:59:39 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA18491; Sun, 28 Sep 1997 15:59:35 -0700 (MST) From: Terry Lambert Message-Id: <199709282259.PAA18491@usr07.primenet.com> Subject: Re: ee taking up weird cpu amount. To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 28 Sep 1997 22:59:35 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970928002450.TG36648@uriah.heep.sax.de> from "J Wunsch" at Sep 28, 97 00:24:50 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > The foreground process group gets properly signalled. I've been using > > > a FreeBSD-based ISP for long enough to know that it works. > > > > Then under what circumstances is it ever possible to get a process > > buzzing in a "read returns 0 bytes" loop? > > The process was in the background, thus in a different process group. Why isn't it "stopped on tty input" instead? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.