When will my application receive SIGPIPE?
- 1 Answers
- 1622 Views
- I also Faced
- E-Mail Answers
Answer / chaitanya
Very simple: with TCP you get SIGPIPE if your end of the connection has received an RST from the other end. What this also means is that if you were using select instead of write, the select would have indicated the socket as being readable, since the RST is there for you to read (read will return an error with errno set to ECONNRESET).
Basically an RST is TCP's response to some packet that it doesn't expect and has no other way of dealing with. A common case is when the peer closes the connection (sending you a FIN) but you ignore it because you're writing and not reading. (You should be using select.) So you write to a connection that has been closed by the other end and the oether end's TCP responds with an RST.
| Is This Answer Correct ? | 0 Yes | 0 No |
How does unix socket work?
Why do we need socket programming?
How come select says there is data, but read returns zero?
What exactly does SO_LINGER do?
What is the difference between read() and recv()?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
How come only the first part of my datagram is getting through?
What is socket address?
Why do I get EPROTO from read()?
of the socket? Does doing a connect() call affect the receive behaviour?
How can I listen on more than one port at a time?
Why do we need sockets?
Unix Commands 
