| commit | ca57de3e7b5ea23e9e1ec51cb33637334196b52f | [log] [tgz] |
|---|---|---|
| author | Willy Tarreau <w@1wt.eu> | Fri Nov 23 20:08:09 2012 +0100 |
| committer | Willy Tarreau <w@1wt.eu> | Fri Nov 23 20:21:37 2012 +0100 |
| tree | 4950952d6614ee5c9b5f11d2214ea6ca0cf13c86 | |
| parent | cfd97c6f043fb64980529a0ce26b10fecd0e8fe2 [diff] |
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.