All existing processes will be counted against this limit, not just new processes to be started. Tips: Set it high enough to exclude all groups used by system users.ĭescription: Limits the total number of processes that can be created on behalf of a user. For example, in a shared hosting environment, LiteSpeed runs as user "If Force GID is set to "nogroup" (or any group other than 'The server, on the other hand, still can serve files under any user's docroot directory (because of its group ID). This can be used to prevent an external application from accessing files owned by other users. When set to non-zero value, all suEXEC external applications (CGI/FastCGI/LSAPI) will use this group ID. Set to a high value when you are performing benchmark tests with a large number of concurrent client machines.ĭescription: Specifies a group ID to be used for all external applications started in suEXEC mode. Trusted IPs or sub-networks are not affected. Tips: A lower number will enable serving more distinct clients. The recommended limit is between 5 and 10. Make sure the limit is set properly, as not to adversely affect normal service.
HTTP/1.1 clients may also set up multiple connections to speed up downloading and SSL requires separate connections from non-SSL connections. You would want to allow those connections for a short period. For example, if a page contains many small graphs, the browser may try to set up many connections at same time, especially for HTTP/1.0 clients. If number of connections is still over the limit after the Grace Period (sec), that IP will be blocked for the Banned Period (sec). This soft limit can be exceeded temporarily during Grace Period (sec) as long as the number is below the Connection Hard Limit, but Keep-Alive connections will be closed as soon as possible until the number of connections is lower than the limit. Description: Specifies the soft limit of concurrent connections allowed from one IP.
0 kommentar(er)
