From owner-freebsd-questions Wed May 22 22:13:35 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA16613 for questions-outgoing; Wed, 22 May 1996 22:13:35 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA16607; Wed, 22 May 1996 22:13:33 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id WAA00930 ; Wed, 22 May 1996 22:13:19 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA07307; Thu, 23 May 1996 14:56:14 +0930 From: Michael Smith Message-Id: <199605230526.OAA07307@genesis.atrad.adelaide.edu.au> Subject: Re: runaway processes To: sfinn@thecore.com (Shaun Finn) Date: Thu, 23 May 1996 14:56:12 +0930 (CST) Cc: gpalmer@FreeBSD.ORG, gfoster@gfoster.com, questions@FreeBSD.ORG In-Reply-To: from "Shaun Finn" at May 22, 96 07:45:52 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Shaun Finn stands accused of saying: > > >> When a user logs off without exiting pine the processes begin using > >> lots of CPU and cannot be killed with -INT. Has a fix or workaround > >> been developed for this? (Yeah, I know, don't run pine :-)! > > > >This is a bug in pine. Try ``kill -9 ''. That should do it nicely > >:-) There is an update to pine (if I remember), but the new version > >may have other problems too... > > We have used pine 3.91 thru 3.93 and the problem persists ;-) > > Even rtin 1.3 950824BETA PL0 displays this behavior. It's not like it's not _documented_ or anything. From the read(2) manpage: RETURN VALUES If successful, the number of bytes actually read is returned. Upon read- ing end-of-file, zero is returned. Otherwise, a -1 is returned and the global variable errno is set to indicate the error. The problem is that the losers who wrote the stuff never bothered to test for this; they expect an error condition on stdin instead. The correct fix is for you to hunt down all the places in the offending programs where read() is called on stdin and patch them to check for '0' return, and then pester the maintainers and forward patches to the ports people. Otherwise this will never be fixed. > | Shaun M. Finn TechnoCore Communications, Inc. | -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[