Send SIGPIPE when writing to a closed pipe/socket

[amscanne]

man 2 write:

"EPIPE fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIGPIPE signal. (Thus, the write return value is seen only if the program catches, blocks or ignores this signal.)"

As is typical, the man page oversimplifies things. For sockets there are three different behaviors (that I've found so far):

SOCK_STREAM: returns EPIPE and sends SIGPIPE
SOCK_SEQPACKET: returns EPIPE and does not send SIGPIPE
SOCK_DGRAM: return ECONNREFUSED and does not send SIGPIPE

[prattmic]

Note: those semantics are for UDS. I'm not sure about TCP, UDP, or other types of sockets.

[milantracy]

I will pick up the issue per my discussion with @nlacasse

I picked up the issue at bugnizer, it looks like that it only mirrored the Github.
I simply let you guys know so that we won't have conflicts on the issue