mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-23 23:01:24 +02:00
a215be282d
Just like for inherited sockets, we want to make sure that FDs that are mentioned in "sockpair@" are actually usable. Right now this test is performed by the callers, but not everywhere. Typically, the following config will fail if fd #5 is not bound: frontend bind sockpair@5 But this one will pass if fd #6 is not bound: backend server s1 sockpair@6 Now both will return an error in such a case: - 'bind' : cannot use file descriptor '5' : Bad file descriptor. - 'server s1' : cannot use file descriptor '6' : Bad file descriptor. As such the test in str2listener() is not needed anymore (and it was wrong by the way, as it used to test for the socket by overwriting the local address with a new address that's made of the FD encoded on 16 bits and happens to still be at the same place, but that strictly depends on whatever the kernel wants to put there).
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)