Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
50 lines (41 sloc) 1.46 KB
__NAME__ purpose
specify whether Interchange server should pre-fork processes that wait for client connections
__NAME__ see also
StartServers, PreForkSingleFork
__NAME__ synopsis
<group choice='plain'>
<arg choice='plain'>No</arg>
<arg choice='plain'>Yes</arg>
__NAME__ description
For each new client connection, &IC; must spawn a new process that will
handle communication with the client.
By using &conf-PreFork;, it is possible to <emphasis>pre-fork</emphasis>
(or in other words, "start ahead of time") some number of &IC; servers
that will be ready to serve client requests immediately as they come in.
If you're running PreFork, you should use it in combination with
&conf-PreForkSingleFork;, to create the absolute minimal number of forks
necessary. Only turn &conf-PreForkSingleFork; off
if it causes zombie processes to pile up.
This method reduces system overhead due to forking and is the fastest and
best way to run a busy &IC; server.
__NAME__ notes
Regardless of the &conf-PreFork; setting, each spawned server will serve
&conf-MaxRequestsPerChild; requests, before being shut down and respawned.
(This technique is used to prevent any memory leaks).
For an introduction to &IC; run modes and practical implications, please
see the &glos-ic-run-mode; glossary entry.
__NAME__ example: Enabling PreFork
PreFork yes
PreForkSingleFork yes
Something went wrong with that request. Please try again.