mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-19 00:51:37 +01:00
6c7e96a3e1
Revert commit fe4abe62c7c5206dff1802f42d17014e198b9141. The goal was to make sure for health-checks, we would not get sockets in TIME_WAIT. To do so, we would not call shutdown() if linger_risk is set. However that is wrong, and that means shutw would never be forwarded to the server, and thus we could get connection that are never properly closed. Instead, to fix the original problem as described here : https://www.mail-archive.com/haproxy@formilux.org/msg34080.html Just make sure the checks code call cs_shutr() before calling cs_shutw(). If shutr has been called, conn_sock_shutw() will make no attempt to call shutdown(), as it knows close() will be called. We should really review and revamp the shutr/shutw code, as described in github issue #142. This should be backported to 1.9 and 2.0.
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)