Xref: utzoo comp.sys.next:13102 comp.os.mach:772 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!mtxinu!sybase!ohday!tim From: tim@ohday.sybase.com (Tim Wood) Newsgroups: comp.sys.next,comp.os.mach Subject: Re: Read timeouts in threads Message-ID: <12395@sybase.sybase.com> Date: 20 Feb 91 18:18:35 GMT References: <16593@milton.u.washington.edu> Sender: news@Sybase.COM Organization: Sybase, Inc. Lines: 17 In article <16593@milton.u.washington.edu> wiml@milton.u.washington.edu (William Lewis) writes: > > I'm trying to get a (small amount of data) from the serial port >on the NeXT, /dev/cu?. Most of the time there should be something there >within a few milliseconds, but in the event that read() blocks for >much time, I want to wake up and report this as an error. Does NeXT have the select() system call? That allows a blocking poll for I/O with a timeout, which seems to be what you want. -TW Sybase, Inc. / 6475 Christie Ave. / Emeryville, CA / 94608 415-596-3500 WORK:tim@sybase.com {pacbell,pyramid,sun,{uunet,ucbvax}!mtxinu}!sybase!tim PLAY:axolotl!tim@toad.com {sun,uunet}!hoptoad!axolotl!tim Dis claim er dat claim, what's da difference? I'm da one doin da talkin' hea. Brought to you by Super Global Mega Corp .com