Hi!

Thanks for answer fpmurphy!
You have right, this is impossible to CLOSE socket and then read from this socket any confirmation about disconnection... but I found solution for my problem -> let's focus on my additional question:
"How to start disconnecting procedure, without closing socket?" -> This is possible.
I didn't share all information about case that I try to resolve, but to make my solution helpful for others, let's say that you are in situation, when server sent all information to client, and now client don't have more requests. Time to close connection, but as in my case, client have to be sure, that server really close connection (in non-blocking tcp type). What I did:
In client I call shutdown(SHUT_WR). This inform server, that client want to close connection (select on server side inform, that there is data to read on socket, but after read it server got 0 -> no more information from client -> disconnection!). So server close socket permanently. Because of this, client got 0 after select + read procedure on the same socket -> server finished disconnection! Now client close socket too, and make new connection on other socket without a problem!
Case solved!

Thanks for everyone for reading this thread, especially fpmurphy.

Ikeban