As discussed earlier the usage can be limited generally using the said techniques, here is few that should set the limitations and to provide good performance to the server. The tag RLimitNPROC is another useful tool in case of an active shared server. This will be effective in the case of apache servers which does have the suexec enabled, thereby to limit the number of processes active by users or for a specific userID. It accepts one or two arguments, namely they will be the soft and hard limits for the user processes.
RLimitNPROC soft-processes [hard-processes]
eg: RLimitNPROC 2 10
should be ideal for a normal running server with high number of users active on apache server.
It will be accepting the value as 'max' and this will be limiting the amount of processes as defined on the root of the system. Again, this will be a dangerous function to use if the CGI's are to run on the apache userID, and the function will be limiting the number of apache ID's created and the situation may rise where you will find the error message " cannot fork " on the apache server.
So when used wisely this will be a very effective tool on the apache based servers with suexec and also have the use on forums.
0 comments:
Post a Comment