hi friends,
is there any way to find the recv() side socket descriptor that its peer is closed at the other side ..
server will keep sending and client will receives it ... if client process closed i can get errno :EPIPE
but if the server process closed .. recv() in client will receive just value '0' and return sucess ....

is there any other way to find the recv socket property to tell the user that peer process is closed on the other side ...

i try poll() checking POLLRDHUP but in vain ... is there any other way left to find ...

because i want to show the user that the peer process is closed at the other side in recv() on client.c

please help me ...

It's a while ago that I did some socket programming, but if I remember correctly, I did the following:

I used a select (poll will also work I assume) to detect that there is a read event on a socket. If the number of bytes read is zero, the connection is closed.

Note: There is a dedicated programming section here at LQ where you're question might have fitted better. Just an idea for the next time that you have a programnming related question.

first thanks for reply ..
yes but i need to differentiate how the connection is closed ...
if the network failed ..or the peer process died ...

i will use your select suggestion and report if succeed ...

If you use a select and the network died, I doubt that select will indicate that there is a read event on that socket. So that one will catch the situation where the peer process died.

Your description in the first post indicates that it's one-way communication (server sends, client receives).
I think that you need to add two-way comms so the client can, at regular intervals) send a message to the server to check if it's still there and the server needs to reply. No reply or send errors indicate a network problem.

i solved the network problem with ioctl call of the device ... but only the peer process i not yet resolved ... i will try this select read call .. thanks for reply ...