Interested to Buy Any Domain ? << Click Here >> for more details...
When will my application receive SIGPIPE?
- 1 Answers
- 2367 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 |
What exactly is a socket?
What is a socket address?
How come I get address already in use from bind()?
Why does it take so long to detect that the peer died?
How can I find the full hostname (FQDN) of the system I am running on?
How do I get my server to find out the clients address / host- name?
Is a socket a file?
How can I write a multi-homed server?
Why does connect() succeed even before my server did an accept()?
How come select says there is data, but read returns zero?
What is a socket file?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
Unix Commands 
