When will my application receive SIGPIPE?
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 |
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
How many sockets can a port have?
How can I bind() to a port number < 1024?
Is a socket a file?
Is socket a hardware or software?
Where is the socket located?
Why does it take so long to detect that the peer died?
What is a socket set used for?
What's the difference between a socket and a port?
How can I set the timeout for the connect() system call?
What is socket address with example?
How can I read only one character at a time?