From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Thu Feb 11 1999 - 18:27:29 EST
On Feb 11, 1999, Godmar Back <gback@cs.utah.edu> wrote:
> But that's a bug in Linux, isn't it? If I successfully select on a
> socket, I should never get an EAGAIN/EWOULDBLOCK on a subsequent
> read().
Maybe there *is* data, but not as much as requested. In this case,
should it read as much as is available and return or return
EWOULDBLOCK? Is this system-dependent?
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:58:06 EDT