One more thing. With this output
WKWWKWRKKRKWWKWWRWWRRKWWKRWKKR.RWR._W_R.RKRKK.RCWWKW_R.W..KKWWK.
WCWKKK_KWWWRR.R..WWKWWRK.WWWRRW.WWW.WRK_WR.R..KWWKKRW.KCWK.W
..R_..WW
On Wed, Jul 8, 2020 at 7:49 AM Mahmood Naderan
wrote:
>
>
> >But it's more straightforward to use /server-status if you care about
> >things like ServerLimit then trying to reverse engineer from netstat.
>
>
>
> OK I can see that report.
>
> It is saying that 109 requests currently being
>But it's more straightforward to use /server-status if you care about
>things like ServerLimit then trying to reverse engineer from netstat.
OK I can see that report.
It is saying that 109 requests currently being processed., 18 idle workers.
Is that 109 the same as the number of apache2
On Wed, Jul 8, 2020 at 5:44 AM Mahmood Naderan
wrote:
>
> Hello
>
> When I set ServerLimit to 500, does that include all TCP connection states? I
> mean
> are all these counted by ServerLimit? Or just ESTABLISHED is counted?
>
>
> tcp6 0 0 192.168.168.91:443 X:18212 FIN_WAIT2
Hello
When I set ServerLimit to 500, does that include all TCP connection states? I
mean
are all these counted by ServerLimit? Or just ESTABLISHED is counted?
tcp6 0 0 192.168.168.91:443 X:18212 FIN_WAIT2 -
tcp6 0 0 192.168.168.91:443 X:14756 TIME_WAIT
