CGIStub Processes (UNIX/Linux)

You can adjust the CGIStub parameters on UNIX/Linux systems. In Sun Java System Web Server, the CGI engine creates CGIStub processes as needed. On systems that serve a large load and rely heavily on CGI-generated content, it is possible for the CGIStub processes to consume all system resources. If this is happening on your server, the CGIStub processes can be tuned to restrict how many new CGIStub processes can be spawned, their timeout value, and the minimum number of CGIStub processes that will be running at any given moment.

If you have an init-cgi function in the magnus.conf file and you are running in multi-process mode, you must add LateInit = yes to the init-cgi line.

The four directives and their defaults that can be tuned to control Cgistub are:

• MinCGIStubs

• MaxCGIStubs

• CGIStubIdleTimeout

• CGIExpirationTimeout

  MinCGIStubs controls the number of processes that are started by default. The first CGIStub process is not started until a CGI program has been accessed. The default value is 2. If you have a init-cgi directive in the magnus.conf file, the minimum number of CGIStub processes are spawned at startup.

  MaxCGIStubs controls the maximum number of CGIStub processes the server can spawn. This is the maximum concurrent CGIStub processes in execution, not the maximum number of pending requests. The default value shown should be adequate for most systems. Setting this too high may actually reduce throughput. The default is 10.

  CGIStubIdleTimeout causes the server to kill any CGIStub processes that have been idle for the number of seconds set by this directive. Once the number of processes is at MinCGIStubs, it does not kill any more processes. The default is 45.

  CGIExpirationTimeout limits the maximum time in seconds that CGI processes can run.

Tuning

You can set the CGIStub processes by:

• Editing them in magnus.conf

• Setting or changing their values in the Magnus Editor of the Server Manager