mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-11-26 21:31:01 +01:00
1f60133bfb
Ilya reported in issue #2193 that the latest Fedora complains about us passing NULL to epoll_wait() in the "debug dev fd" code to try to detect an epoll FD. That was intentional to get the kernel's verifications and make sure we're facing a poller, but since such a warning comes from the libc, it's possible that it plans to replace the syscall with a wrapper in the near future (e.g. epoll_pwait()), and that just hiding the NULL (as was confirmed to work) might just postpone the problem. Let's take another approach, instead we'll create a new dummy FD that we'll try to remove from the epoll set using epoll_ctl(). Since we created the FD we're certain it cannot be there. In this case (and only in this case) epoll_ctl() will return -ENOENT, otherwise it will typically return EINVAL or EBADF. It was verified that it works and doesn't return false positives for other FD types. It should be backported to the branches that contain a backport of the commit which introduced the feature, apparently as far as 2.4: 5be7c198e ("DEBUG: cli: add a new "debug dev fd" expert command")
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)