commit | 7e4086dc183fb4e1db619b6e4394c7644e388542 | [log] [tgz] |
---|---|---|
author | Willy Tarreau <w@1wt.eu> | Sun Feb 02 01:44:13 2014 +0100 |
committer | Willy Tarreau <w@1wt.eu> | Sun Feb 02 09:38:06 2014 +0100 |
tree | f9291608caebf5e864aa19c27fa4b10af9e1e3b7 | |
parent | d8b2bb5c05e64c65ea3a6c9c69e719d853a667ad [diff] |
BUG/MINOR: raw_sock: correctly set the MSG_MORE flag Due to a typo, the MSG_MORE flag used to replace MSG_NOSIGNAL and MSG_DONTWAIT. Fortunately, sockets are always marked non-blocking, so the loss of MSG_DONTWAIT is harmless, and the NOSIGNAL is covered by the interception of the SIGPIPE. So no issue could have been caused by this bug.