Re: PROBLEM: select() says closed socket readable

From: kuznet@ms2.inr.ac.ru
Date: Sat Aug 18 2001 - 11:27:47 EST

Next message: Alexey Kuznetsov: "Re: connect() does not return ETIMEDOUT"
Previous message: Matthias Schniedermeyer: "Re: Strange Slowdown"
In reply to: Jay Rogers: "PROBLEM: select() says closed socket readable"
Next in thread: Ton Hospel: "Re: PROBLEM: select() says closed socket readable"
Reply: Ton Hospel: "Re: PROBLEM: select() says closed socket readable"
Reply: Jay Rogers: "Re: PROBLEM: select() says closed socket readable"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello!

> For linux 2.4.2, select() indicates socket ready for read on a
> socket that's never been connected.

Right. It does not block on read, hence it is readable.

> This is inconsistent

This is perfectly consistent. Reaction to bugs in applications
is undefined.

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

Next message: Alexey Kuznetsov: "Re: connect() does not return ETIMEDOUT"
Previous message: Matthias Schniedermeyer: "Re: Strange Slowdown"
In reply to: Jay Rogers: "PROBLEM: select() says closed socket readable"
Next in thread: Ton Hospel: "Re: PROBLEM: select() says closed socket readable"
Reply: Ton Hospel: "Re: PROBLEM: select() says closed socket readable"
Reply: Jay Rogers: "Re: PROBLEM: select() says closed socket readable"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:28 EST