Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.com!imci4!newsfeed.internetmci.com!news.mathworks.com!fu-berlin.de!cs.tu-berlin.de!informatik.uni-bremen.de!nordwest.pop.de!uniol!uni-erlangen.de!news.tu-chemnitz.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Pine uses huge amount of cpu time - why? Date: 4 Apr 1996 21:35:08 GMT Organization: Private BSD site, Dresden Lines: 18 Message-ID: <4k1fac$krb@uriah.heep.sax.de> References: <4jbvau$mrs@chenab.lums.edu.pk> <4jdkpc$712@charm.il.ft.hse.nl> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.3 robert@il.ft.hse.nl (robert) writes: > It's not only PINE that does this. I think it has to do with the > program not being able to write to the tty it was on (which, when the > telnetd died, got disowned), and therefore going into an infinite, quite > cpu-extensive, write-loop. I think it's rather a read loop. These programs seem to ignore an error condition when reading from a stale tty file descriptor. (Ignoring an error condition on output is not fatal, but treating an input error as null input, and repeating the input attempt is fatal.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)