Re: PROBLEM: a local TCP socket close does not trigger a poll on the other end

[kuznet@xxxxxxxxxxxxx]

Hello!

> This is not fair at all, because the socket is informed that the other end 
> has 
> closed, so it is possible to trigger the poll.

It is triggered. You masked the event. POLLIN.
It is normal _maskable_ event, not an error and not an out of band data.


> Writing successfully to a socket when the other end is closed

Write will fail in the case, if other end happened to be fully closed.
Seems, you think that tcp is a psychic. Alas, this poor guy is not a psychic
and can distingusih close and half close only actively or if it is implied
by application level protocol. See? You _must_ write something to detect
death of other end or you must close actively yourself.

Alexey