I've been using this library in some production code, and my Bug logging software has been picking up a lot of SIGPIPE 13 errors from this library on sends.
It looks in part due to the socket unexpectedly closing on our side (I was keeping the connection open for far too long), but given that the code has inbuilt error checking on the SendTo operation, it should be safe to disable the SIGPIPE errors in this way.
I've been using this library in some production code, and my Bug logging software has been picking up a lot of SIGPIPE 13 errors from this library on sends.
It looks in part due to the socket unexpectedly closing on our side (I was keeping the connection open for far too long), but given that the code has inbuilt error checking on the SendTo operation, it should be safe to disable the SIGPIPE errors in this way.