EAGAIN error after poll said that socket is read ready

From: Andrei Voropaev (avorop_at_mail.ru)
Date: 10/30/03 

Date: 30 Oct 2003 14:08:31 GMT

Hi!

This is just curiosity question. I didn't expect that after poll
indicated that my socket had POLLIN event my recv would return EAGAIN
error. But it happened to me today. And not once. The fact that it
happens only today while the program is running for couple months adds
to my confusion. So, is it possible that after poll indicated read
readinnes actuall read would return EAGAIN for non-blocking socket?

Andrei

Relevant Pages

  • Re: EAGAIN error after poll said that socket is read ready
    ... >> indicated that my socket had POLLIN event my recv would return EAGAIN ... is it possible that after poll indicated read ... that there's some kind of memory corruption. ...
    (comp.os.linux.development.apps)
  • Re: EAGAIN error after poll said that socket is read ready
    ... > indicated that my socket had POLLIN event my recv would return EAGAIN ... is it possible that after poll indicated read ...
    (comp.os.linux.development.apps)
  • Re: recv returns 0; errno = EAGAIN
    ... > I have a recv call to a socket and the return value from recv is 0 and ... > the errno is EAGAIN. ... > What are the chances of recv returning 0 and EAGAIN? ... the socket connection. ...
    (comp.unix.programmer)
  • Re: EAGAIN mystery
    ... > I saw that a particular server socket was continuously returning on ... > poll() but when it does an accept, it comes back with EAGAIN. ... but when the socket does an accepton non-blocking ...
    (comp.unix.programmer)
  • Re: recv returns 0; errno = EAGAIN
    ... > I have a recv call to a socket and the return value from recv is 0 and ... > the errno is EAGAIN. ... > What are the chances of recv returning 0 and EAGAIN? ...
    (comp.unix.programmer)