Read from TCP socket with broken connection.

[Eric Norum]

Sergei Organov wrote:
> 
> When a socket was connected but remote host has closed connection, how
> subsequent read/write operations should behave? My observation is that read()
> returns 0 and doesn't set 'errno'. Is it correct behavior?

Yes.

> 
> If yes, then how do I distinguish between reading from such a socket and
> reading from connected socked that results in time-out with zero bytes
> received? Or, alternatively, how to detect that remote host has closed
> connection?

If you've used setsockopt to set a receive timeout and the sender
doesn't transmit within that time limit the read will return an error
(-1) with errno set.  Otherwise a read will block forever if the remote
machine terminates without closing down the socket (unless you've turned
on KEEPALIVE messages).
-- 
Eric Norum                                 eric.norum at usask.ca
Department of Electrical Engineering       Phone: (306) 966-5394
University of Saskatchewan                 FAX:   (306) 966-5407
Saskatoon, Canada.