From owner-freebsd-hackers Sun Sep 28 15:45:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27901 for hackers-outgoing; Sun, 28 Sep 1997 15:45:16 -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 PAA27867 for ; Sun, 28 Sep 1997 15:44:50 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA17978; Sun, 28 Sep 1997 15:44:28 -0700 (MST) From: Terry Lambert Message-Id: <199709282244.PAA17978@usr07.primenet.com> Subject: Re: ee taking up weird cpu amount. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 28 Sep 1997 22:44:27 +0000 (GMT) Cc: tlambert@primenet.com, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: <27013.875412811@time.cdrom.com> from "Jordan K. Hubbard" at Sep 27, 97 07:13:31 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Dealing with the error case is only a requirement of FreeBSD and > >several other "broken" systems. The only other one that springs to > > Dealing with I/O errors on reading from the tty is the responsibilty > of any reasonably well written program. Is that a genuine Stetson I > see you talking out of there? Nice hat! ;-) Read my other posting. The only possible errors in this particular read case are related to inpout redirection from a file (EIO). If the read returns a zero, it only does so because SIGHUP processing has not killed the process as it should have in the trampoline code on the way out of the read system call before the call was alloed to return. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.