mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-11-24 04:11:02 +01:00
d52a7f8c8d
When logging to a file descriptor, we'd rather use the unified fd_write_frag_line() which uses the FD's lock than perform the writev() ourselves and use a per-server lock, because if several loggers point to the same output (e.g. stdout) they are still not locked and their logs may interleave. The function above instead relies on the fd's lock so this is safer and will even protect against concurrent accesses from other areas (e.g traces). The function also deals with the FD's non-blocking mode so we do not have to keep specific code for this anymore in the logs.
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)