David Schwartz wrote:
In this case what, will reset the "something interesting has happened"
report from the SELECT call? Will it ever be reset in this case?
Nope. An errored connection is always ready for read/write -- there is
nothing to wait for as far as the kernel is concerned. Your code keeps
asking the kernel if something interesting has happened, the kernel keeps
telling it yes, and it refuses to do anything about it.
Actually its somewhat of a misreading.
The first sentence of the man pages for select suggests that something
interesting has happened inbetween select()'s.
Later on it states "more precisely, to see if a read will not block",
which is still different from "if characters become available for reading".
The "precisely" fits my issue, and not the others.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
