Linux Network programming detailed nine

the cause of sigpipe signal in TCP/IP protocol 1 Suppose that the client socket socket close () will send a byte segment to the server fin; 2 The server receives fin, but does not call close () because the socket has a buffer, so the server can still send data to the client.  3. If the server sends data to the client in this state, it will cause the tcp/IP protocol to reset the RST segment, causing the server to send a sigpipe signal to the current process, and  the default action of Sigpipe signal is to close the current process. so the sigpipe signal must be captured in network programming because it is not sure which end will suddenly close (). 

Linux Network programming detailed nine