mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-22 06:11:32 +02:00
eaefc3c503
When we have a EVFILT_READ event, an optimization was made, and the FD was not reported as ready to receive if there were no data available. That way, if the socket was closed by our peer (the EV8EOF flag was set), and there were no remaining data to read, we would just close(), and avoid doing a recv(). However, it may be fine for TCP socket, but it is not for UDP. If we send data via UDP, and we receive an error, the only way to detect it is to attempt a recv(). However, in this case, kevent() will report a read event, but with no data, so we'd just ignore that read event, nothing would be done about it, and the poller would be woken up by it over and over. To fix this, report read events if either we have data, or the EV_EOF flag is not set. This should be backported to 2.1, 2.0, 1.9 and 1.8.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)