Return to BSD News archive
Xref: sserve comp.os.lynx:134 comp.unix.bsd:13110 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!parc!draco!leisner From: leisner@draco (Marty Leisner 25733) Newsgroups: comp.os.lynx,comp.unix.bsd Subject: Re: select, read and named pipes Followup-To: comp.os.lynx,comp.unix.bsd Date: 18 Dec 1993 16:08:20 GMT Organization: xerox Lines: 28 Message-ID: <2ev9tk$r4q@news.parc.xerox.com> References: <2eit5g$t3i@news.parc.xerox.com> <1993Dec14.192758.26204@wattres.SJ.CA.US> Reply-To: leisner@sdsp.mc.xerox.com NNTP-Posting-Host: draco.sdsp.mc.xerox.com X-Newsreader: TIN [version 1.2 PL2] Steve Watt -- KD6GGD (steve@wattres.SJ.CA.US) wrote: : In article <2eit5g$t3i@news.parc.xerox.com> leisner@sdsp.mc.xerox.com writes: : I hope it gets a read that returns 0, as well. That's the only way to detect : end-of-file, after all. : > 2) on lynx/sparc, it works until the first process terminates : > (closes the pipe). Then select returns a postive response : > (something interesting happened), and read returns 0 (nothing : > to read). : Which is as one would expect, unless it does it continuously. I get continuous selects returned true, read returning 0. (If I got one read of 0, its tolerable). The problem goes away if I open up the pipe R/W and only read from it (in stevens Advanced Unix Programming, he indicates an end of file occurs when the last writer closes its file). -- marty leisner@sdsp.mc.xerox.com leisner.henr801c@xerox.com Member of the League for Programming Freedom "I just know I'm a better manager when I have Joe DiMaggio in center field" -- Casey Stengel