Re: poll() returns POLLIN but no data ?

From: Maxim Yegorushkin (firstname.lastname_at_gmail.com)
Date: 06/26/05

  • Next message: David Schwartz: "Re: poll() returns POLLIN but no data ?" 
    Date: Sun, 26 Jun 2005 23:49:56 +0400

    On Sun, 26 Jun 2005 23:32:46 +0400, David Schwartz <davids@webmaster.com>
    wrote:

    []

    >> Using blocking sockets with select/poll/epoll/... is fine, read/write
    >> won't block if the descriptor has been indicated to be ready for that
    >> operation and this is guarantied by POSIX. Blocking accept() can block
    >> after a socket has been indicated as ready for read because a client
    >> could
    >> bail out before you call accept.
    >
    > It is not guaranteed by POSIX, and it cannot be guaranteed.

    I thought this guaranties that
    http://www.opengroup.org/onlinepubs/009695399/functions/select.html

    Why can't it be guaranteed? 

    -- 
Maxim Yegorushkin
<firstname.lastname@gmail.com>
  • Next message: David Schwartz: "Re: poll() returns POLLIN but no data ?"

    Relevant Pages

    • Re: poll() returns POLLIN but no data ?
      ... David has a different idea about what "blocking" means than many other ... "A descriptor shall be considered ready for reading when a call to ... So whatever you define as blocking the standard says it won't. ...
      (comp.unix.programmer)
    • Re: poll() returns POLLIN but no data ?
      ... >> It is not guaranteed by POSIX, ... that time and when you actually call the input/output function, ... checking for readability of the same stream. ...
      (comp.unix.programmer)