4 ms·
If I understand it correctly, the issue was’t caused by not checking the result of sendmsg, but sendmsg blocking the program when the send buffer was full.
by eeeeffdsx 8y ago
If I understand it correctly, the issue was’t caused by not checking the result of sendmsg, but sendmsg blocking the program when the send buffer was full.
- muststopmyths 8y agono, if you look at the github issue, sendmsg fails with EAGAIN. It's probably an upper layer that hangs.
- noselasd 8y agoNote that in this case EAGAIN is just an indication the socket buffer is full - which can easily also happen on normal operation when you're blasting off calls at full speed.