mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-01-19 20:20:45 +00:00
haproxy public development tree
a9aa628703
Till now the fuzzy matching would only work on the same number of words, but this doesn't account for commands like "show servers conn" which involve 3 words and were not proposed when entering only "show conn". Let's improve the situation by building the two fingerprints separately for the correct keyword sequence and the entered one, then compare them. This can result in slightly larger variations due to the different string lengths but is easily compensated for. Thanks to this, we can now see "show servers conn" when entering "show conn", and the following choices are relevant to correct typos: - "show foo" show sess [id] : report the list of current sessions or dump this session show info : report information about the running process [desc|json|typed]* show env [var] : dump environment variables known to the process show fd [num] : dump list of file descriptors in use show pools : report information about the memory pools usage - "show stuff" show sess [id] : report the list of current sessions or dump this session show info : report information about the running process [desc|json|typed]* show stat : report counters for each proxy and server [desc|json|no-maint|typed|up]* show fd [num] : dump list of file descriptors in use show tasks : show running tasks - "show stafe" show sess [id] : report the list of current sessions or dump this session show stat : report counters for each proxy and server [desc|json|no-maint|typed|up]* show fd [num] : dump list of file descriptors in use show table [id]: report table usage stats or dump this table's contents show tasks : show running tasks - "show state" show stat : report counters for each proxy and server [desc|json|no-maint|typed|up]* show servers state [id]: dump volatile server information (for backend <id>) It's still visible that the shorter ones continue to easily match, such as "show sess" not having much in common with "show foo" but what matters is that the best candidates are definitely relevant. Probably that listing them in match order would further help. |
||
|---|---|---|
| .github | ||
| contrib | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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)