Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!wuarchive!udel!princeton!phoenix.Princeton.EDU!subbarao
From: subbarao@phoenix.Princeton.EDU (Kartik Subbarao)
Newsgroups: comp.unix.questions
Subject: Re: A question about read() system call!!
Message-ID: <azaC8VCoBMwpU@idunno.Princeton.EDU>
Date: 23 May 91 13:02:28 GMT
References: <28398698.26968@maccs.dcss.mcmaster.ca> <690002@hpsciz.sc.hp.com> <1361@anprda.atson.asahi-np.co.jp>
Sender: news@idunno.Princeton.EDU
Reply-To: subbarao@phoenix.Princeton.EDU (Kartik Subbarao)
Organization: American Chemical Society
Lines: 26

In article <1361@anprda.atson.asahi-np.co.jp> akira@anprda.atson.asahi-np.co.jp (Akira Takiguchi) writes:

>>If the file is not open yet, you can specify the O_NDELAY option when you
>>open the file.
>
>     This has nothing to do with the problem.  It makes open(2) non-blocking
>but not read(2).

Not on all types of machines. From our open(2v) man page: (SunOS 4.1.1)

     If the O_NDELAY or O_NONBLOCK flag  is  set  on  a  call  to
     open(),   the  corresponding  flag  is  set  for  that  file
     descriptor (see fcntl(2V)) and subsequent reads  and  writes
     to   that  descriptor  will  not  block  (see  read(2V)  and
     write(2V)).


		-Kartik


--
internet% ypwhich

subbarao@phoenix.Princeton.EDU -| Internet
kartik@silvertone.Princeton.EDU (NeXT mail)  
SUBBARAO@PUCC.BITNET			          - Bitnet