MaxKeepAliveRequests,MaxRequestsPerChild, ListenBacklog, MaxSpareServers, MinSpareServers: Some more quick limiting options

ListenBackLog: Used to define the maximum length of the queue of pending connections.

format:ListenBacklog 100

Normally the settings are tuned fine and should be able to work along with the normal running. But in special cases like constant TCP SYN attacks that are to act on the server, the enty will be effective in controlling the access. Most of the occassions will not require the number to be set out as specified since the operating systems may restrict the number of access using the system call 'Listen' clause and this should be much lesser a number than the current one. Again, there is the factor of operating system and this should change with each running operating system. The number may be higher at some instances that the ones specified in the example.

MaxKeepAliveRequests: Defines the the keep-alive requests per connection made on to the server.

MaxKeepAliveRequests 20

The directive is used to limit the number of keep-alive requests that are to arrive from a particular TCP/IP connection. The situation will be valid when the clause KeepAlive On is set on the server else you will find this function close to no use. 0 is used to specify the unlimited access and it is always advised to use high values to obtain maximum performance.

MaxRequestsPerChild : Defines the Number of connections made by server child process

MaxRequestsPerChild 10000

This limit defines the maximum number of child processes created on the server and after the count the new process will die. When the value is set as 0 then the processes does not die automatically. Again for the keep alive requests only the first request counts for the limit and thus will be equally effective with the maxkeepaliverequests clause.

MaxSpareServers : Defines the number of server child processes on the server.

MaxSpareServers 15

This is the count for the maximum number of idle processes by a server, a server process is counted as idle when it fails to serve any requests. The directive mentions the maximum number of idle processes and beyond this count the parent process will automatically kill the idle process.

MinSpareServers: The minimum count of server child processes.

This count is used to define the minimum number or idle processes on the server. If the server finds the count less than the limit then it will be creating a new process at a minimal rate of 1 per second.

MinSpareServers 10