mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-20 14:40:13 +00:00
Event loops: served on by default, the data relayed by the loops
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>
This commit is contained in:
parent
143158e97f
commit
023eb8f830
8 changed files with 33 additions and 18 deletions
2
.github/workflows/c-cpp-Linux.yml
vendored
2
.github/workflows/c-cpp-Linux.yml
vendored
|
|
@ -30,6 +30,8 @@ jobs:
|
|||
run: make -f Makefile.Linux MAILPROXY=true FTP=true
|
||||
- name: regression tests
|
||||
run: python3 tests/run.py
|
||||
- name: regression tests, a thread for each client
|
||||
run: python3 tests/run.py --loopmode off
|
||||
- name: mkdir
|
||||
run: mkdir ~/3proxy
|
||||
- name: make install
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue