Table of Contents
Advertisement
CGI
•
CGIExpirationTimeout
•
CGIStubIdleTimeout
•
CGIWaitPid (UNIX Only)
•
MaxCGIStubs
•
MinCGIStubs
CGIExpirationTimeout
This directive specifies the maximum time in seconds that CGI processes are
allowed to run before being killed.
The value of
minutes) would be a good value for most interactive CGIs; but if you have CGIs
that are expected to take longer without misbehaving, then you should set it to the
maximum duration you expect a CGI program to run normally. A value of
disables CGI expiration, which means that there is no time limit for CGI processes.
Note that on Windows NT/Windows 2000 platforms
work, so you must use
Default
0
CGIStubIdleTimeout
This directive 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
Default
30
CGIWaitPid (UNIX Only)
For UNIX platforms, when
signal is the system default action for the signal. If a NSAPI plugin fork/execs a
child process, it should call
enabled to avoid leaving "defunct" processes when its child process terminates.
When
child processes. Note that this directive has no effect on CGI.
276
Netscape Enterprise Server NSAPI Programmer's Guide • April 2002 (Draft)
CGIExpirationTimeout
CGIExpirationTimeout
, the server does not kill any more processes.
is enabled, the SHTML engine waits explicitly on its exec cmd
CGIWaitPid
should not be set too low - 300 seconds (5
.
is set to on, the action for the SIGCHLD
CGIWaitPid
with its child process
waitpid
time-out does not
init-cgi
when
pid
CGIWaitPid
0
is
Advertisement
Table of Contents
