mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-05 09:25:49 +08:00
023eb8f830
loopmode is cb unless a configuration says otherwise, as -L2 had it for a service: its clients on event loops, a connection's data relayed by the loop itself where nothing but the sockets is between its sides. A service whose clients cannot share a thread (threadperclient: PAM, LDAP, FilePlugin, names resolved by the system, -ne) or listening for connections back (-R) still gives each a thread, as do the standalone services and builds without fibers. loopmode on and -L keep the loops with the relay on the client's stack; loopmode off and -L0 a thread for each client. The man page tells of cb. tests/run.py --loopmode takes the mode (cb, on, off) to give every configuration, with two loops; the Linux workflow runs the suite once more with a thread for each client, which is no longer what a configuration gets by default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build-ipk.yml | ||
| build-rpm-arm64.yml | ||
| build-rpm-armhf.yml | ||
| build-rpm-x86-64.yml | ||
| build-watcom.yml | ||
| build-win32.yml | ||
| build-win64.yml | ||
| build-win-msys2-ucrt64.yml | ||
| build-winarm64.yml | ||
| c-cpp-cmake.yml | ||
| c-cpp-Linux.yml | ||
| c-cpp-MacOS.yml | ||
| c-cpp-Windows.yml | ||
| docker-test.yml | ||
| docker.yml | ||
| release-kind.yml | ||
| release-tarball.yml | ||
| update-docs.yml | ||
| update-version.yml | ||
| update-wiki.yml | ||