Re: select implementation not POSIX compliant?

[Alan Cox]

On Gwe, 2004-08-13 at 21:18, Nick Palmer wrote:
> Actually Solaris and Linux are consistent in terms of the behavior of
> select in this respect. I suspect that the first select is blocking the
> socket from being used at all, so the second select can't tell that it
> is closed.

The objects are refcounted so the socket hasn't gone away until the
point the select returns.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/