WHY they are different when checking concurrent limit?

Hi guys: I’m reading the source code of version 1.6.2, in function listener_accept: /* Note: if we fail to allocate a connection because of configured * limits, we'll schedule a new attempt worst 1 second later in the * worst case. If we fail due to system limits or temporary resource *

Re: WHY they are different when checking concurrent limit?

} WHY not using listener_full ? Thanks, zhou 在 15/11/10 下午3:30， "Willy Tarreau" <w...@1wt.eu> 写入: >Hi, > >On Mon, Nov 09, 2015 at 12:46:57PM +, Zhou,Qingzhi wrote: >> if (unlikely(actconn >= global.maxconn) && !(l->options & >>LI_O_UNLIM