9fbcb7e2e9
Since 1.9 we support sending logs to various non-blocking outputs like stdou/stderr or flies, by using writev() which guarantees that it only returns after having written everything or nothing. However the syscall may be interrupted while doing so, and this is visible when writing to a tty during debug sessions, as some logs occasionally appear interleaved if an xterm or SSH connection is not very fast. Performance here is not a critical concern, log correctness is. Let's simply take the logger's lock around the writev() call to prevent multiple senders from stepping onto each other's toes. This may be backported to 2.0 and 1.9.
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)