<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: About PHP_FCGI_MAX_REQUESTS and lighttpd</title>
	<atom:link href="http://blog.jolexa.net/2009/12/20/about-php_fcgi_max_requests-and-lighttpd/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jolexa.net/2009/12/20/about-php_fcgi_max_requests-and-lighttpd/</link>
	<description>Random thoughts and rants...mostly Linux</description>
	<lastBuildDate>Tue, 07 Feb 2012 16:46:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dean Hall</title>
		<link>http://blog.jolexa.net/2009/12/20/about-php_fcgi_max_requests-and-lighttpd/comment-page-1/#comment-2518</link>
		<dc:creator>Dean Hall</dc:creator>
		<pubDate>Thu, 15 Jul 2010 03:06:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=587#comment-2518</guid>
		<description>Actually, the more reading I do, the more I&#039;m convinced that lighttpd&#039;s fastcgi.server is trying to act as a process manager for php-cgi, but php-cgi is too. To keep fastcgi.server from doing process management, I would guess &quot;max-procs&quot; and &quot;min-procs&quot; should be &quot;1&quot;, and PHP_FCGI_CHILDREN and PHP_FCGI_MAX_REQUESTS must be set to allow php-cgi to act as its own process manager.</description>
		<content:encoded><![CDATA[<p>Actually, the more reading I do, the more I&#8217;m convinced that lighttpd&#8217;s fastcgi.server is trying to act as a process manager for php-cgi, but php-cgi is too. To keep fastcgi.server from doing process management, I would guess &#8220;max-procs&#8221; and &#8220;min-procs&#8221; should be &#8220;1&#8243;, and PHP_FCGI_CHILDREN and PHP_FCGI_MAX_REQUESTS must be set to allow php-cgi to act as its own process manager.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Hall</title>
		<link>http://blog.jolexa.net/2009/12/20/about-php_fcgi_max_requests-and-lighttpd/comment-page-1/#comment-2517</link>
		<dc:creator>Dean Hall</dc:creator>
		<pubDate>Thu, 15 Jul 2010 02:40:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=587#comment-2517</guid>
		<description>I could be mistaken here, and correct me if I&#039;m wrong, but I think you may be confusing PHP_FCGI_CHILDREN with the -F parameter of spawn-fcgi. By default, spawn-fcgi spawns a single parent process with $PHP_FCGI_CHILDREN children. The wildcard here is the &quot;max-procs&quot; fastcgi configuration parameter in lighttpd itself. When I was using lighttpd, I didn&#039;t use it at all; I merely used PHP_FCGI_CHILDREN to indicate how many children the single parent process should spawn to handle requests, and I usually kept it, depending on the size of the server, between 8 and 32. Actually, I still do, using spawn-fcgi with nginx.</description>
		<content:encoded><![CDATA[<p>I could be mistaken here, and correct me if I&#8217;m wrong, but I think you may be confusing PHP_FCGI_CHILDREN with the -F parameter of spawn-fcgi. By default, spawn-fcgi spawns a single parent process with $PHP_FCGI_CHILDREN children. The wildcard here is the &#8220;max-procs&#8221; fastcgi configuration parameter in lighttpd itself. When I was using lighttpd, I didn&#8217;t use it at all; I merely used PHP_FCGI_CHILDREN to indicate how many children the single parent process should spawn to handle requests, and I usually kept it, depending on the size of the server, between 8 and 32. Actually, I still do, using spawn-fcgi with nginx.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

