Why maxconn value can have a negative value?

Hi, When negative value is given for maxconn(-1,-2...-9, 10.) parameter in global section of haproxy.cfg. It is observed that haproxy service starts with successful health check up of backend servers. But when larger negative value is given then haproxy fails to start and Alert message is shown

Re: segfault in haproxy=1.8.4

Hi! It's been almost 2 weeks since I've installed the patch and there were no segfaults since then. It seems that the problem is fixed now. Thank you! 2018-03-19 23:16 GMT+03:00 William Dauchy : > On Mon, Mar 19, 2018 at 08:41:16PM +0100, Willy Tarreau wrote: > > For me, "experimental" simply me

multithreading issuse in haproxy 1.8.5

I am try to use multithreading w/ haproxy 1.8.5 (on FreeBSD 11-stable) and see high and saw-tooth CPU consume. I am use next config: global nbproc 1 nbthread 2 cpu-map auto:1/1-2 0-1 I am use for comprassion haproxy 1.7.10 w/ next config: global nbproc 2 cp

Re: lua socket api settimeout in seconds vs. milliseconds

Hi Tim, On Mon, Mar 26, 2018 at 12:15:02AM +0200, Tim Düsterhus wrote: > Willy, > > Am 08.03.2018 um 21:15 schrieb Thierry Fournier: > > 3 new patch in attachement to consider for the initial subject of > > this thread. > > > > did you miss these patches from Thierry to the Lua subsystem? Hmmm

Re: lua socket api settimeout in seconds vs. milliseconds

Willy, Am 08.03.2018 um 21:15 schrieb Thierry Fournier: > 3 new patch in attachement to consider for the initial subject of > this thread. > did you miss these patches from Thierry to the Lua subsystem? Best regards Tim Düsterhus

Re: patch: fix build when USE_THREAD is not defined

Илья, Am 24.03.2018 um 19:42 schrieb Илья Шипицин: > in your patch comparision + empty loop will be executed even if USE_THREADS > is not defined. > not very big performance overhead actually. > I'm sure that any compiler able to compile haproxy properly is able to remove the loop as part of it'