c02cefce23
A significant number of actions now take arguments that are evaluated as log-format expressions. Some of them are called "fmt", others "string". The description of the argument sometimes just says "the log-format string" or "log format" or "custom log format" etc. Most of them do not mention the section to visit, and section 8.2 speaking about log-format is very centric on logs usage (the primary use case), making all of this very confusing for newcomers. Since section 8.2.6 is titled "Custom log format" and describes the syntax to be used with the "log-format" (and other) directives, let's call this "Custom log format" everywhere and mention section 8.2.6. When the field was called "string", it was also renamed to "fmt". It doesn't seem worth backporting this, unless it applies fine.
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)