[lkml]   [2001]   [Aug]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: PROBLEM: select() says closed socket readable
David S. Miller wrote:
> From: Jay Rogers <>
> Date: Mon, 20 Aug 2001 10:34:09 -0400
> > Right. It does not block on read, hence it is readable.
> No, a socket that's never been connected isn't readable, hence
> select() shouldn't be returning a value of 1 on it.
> You may read without blocking, select() returns 1.

By this logic a socket that is set non-blocking should always be
treated as readable. I think we can all agree that argument is
flawed :-).

The prevailing view from other systems appears to be that reading
from an unconnected (or unconnectING) socket is meaningless so
the socket is not readable.

Presumably there is a damn good reason, or a standards reference,
why that is the wrong behaviour and should be changed?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:57    [W:0.164 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site