8de7f2822b
The first one will enable all currently deployed BUG_ON() checks. These ones are safe from a performance perspective and from a reliability perspective. New ones may be added later with different categories (hot path, detection of uncertain events, etc). DEBUG_MEMORY_POOLS enables the "tag" pool debugging option by default, so that pools may be better traced in dumps. This one alone results in almost imperceptible performance difference, and 8 extra bytes per allocated object. Both options are safe for production use (they're among those enabled all the time on haproxy.org) and allow to produce much more trustable bug reports which should save a few round trips with the reporters.
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)