4931d1ca5f
During re-execution master keeps always opened "reload" sockpair FDs and shared sockpair ipc_fd[0], the latter is using to transfert listeners sockets from the previously forked worker to the new one. So, these master's FDs are inherited in the newly forked worker and must be closed in its context. "reload" sockpair inherited FDs and shared sockpair FD (ipc_fd[0]) are closed separately, becase master doesn't recreate "reload" sockpair each time after its re-exec. It always keeps the same FDs for this "reload" sockpair. So in worker context it can be closed immediately after the fork. At contrast, shared sockpair is created each time after reload, when the new worker will be forked. So, if N previous workers are still exist at this moment, the new worker will inherit N ipc_fd[0] from master. So, it's more save to close all these FDs after get_listeners_fd() and bind_listeners() calls. Otherwise, early closed FDs in the worker context will be immediately bound to listeners and we could potentially have some bugs.
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.