BUG/MAJOR: peers: the listener's maxaccept was not set and caused loops

Recent commit 16a214 to move the maxaccept parameter to listeners didn't
set it on the peers' listeners, resulting in the value zero being used
there. This caused a busy loop for each peers section, because no incoming
connection could be accepted.

Thanks to Hervé Commowick for reporting this issue.

diff --git a/src/cfgparse.c b/src/cfgparse.c
index c31774320235b5a210982bc4d15533801c5193e1..9fa1881921ff15b5e8ce94f21b7d68709d22eb78 100644 (file)
--- a/src/cfgparse.c
+++ b/src/cfgparse.c
@@ -7135,6 +7135,7 @@ out_uri_auth_compat:
                while (*last) {
                        curpeers = *last;
                        if (curpeers->peers_fe) {
+                               LIST_NEXT(&curpeers->peers_fe->conf.listeners, struct listener *, by_fe)->maxaccept = 1;
                                last = &curpeers->next;
                                continue;
                        }