<?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: Issue and solution for upgrading Lighttpd from 1.4.8 to 1.4.11</title>
	<atom:link href="http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411/feed" rel="self" type="application/rss+xml" />
	<link>http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411</link>
	<description>Anecdotes on Technology Leadership, Ruby, Java, Scala, Cloud Computing, Open-Source, SEO, and Design</description>
	<lastBuildDate>Sun, 20 May 2012 19:43:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sebastian Burkhart</title>
		<link>http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411/comment-page-1#comment-33156</link>
		<dc:creator>Sebastian Burkhart</dc:creator>
		<pubDate>Thu, 10 May 2007 08:52:18 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411#comment-33156</guid>
		<description>This seems to happen when the shebang line of the dispatcher script doesn&#039;t reference to an existing interpreter.

Find the corresponding first line in the dispatch.fcgi file, e.g.:

#!/opt/local/non/existing/path/to/ruby

and test if the interpreter is to be found there. If not, change it to the right path, e.g.:

#!/usr/bin/ruby

The error message for wrong shebang lines is generally a bit misleading, as it suggests that the script file itself is not found - even if it&#039;s only the referenced interpreter that is missing.</description>
		<content:encoded><![CDATA[<p>This seems to happen when the shebang line of the dispatcher script doesn&#8217;t reference to an existing interpreter.</p>
<p>Find the corresponding first line in the dispatch.fcgi file, e.g.:</p>
<p>#!/opt/local/non/existing/path/to/ruby</p>
<p>and test if the interpreter is to be found there. If not, change it to the right path, e.g.:</p>
<p>#!/usr/bin/ruby</p>
<p>The error message for wrong shebang lines is generally a bit misleading, as it suggests that the script file itself is not found &#8211; even if it&#8217;s only the referenced interpreter that is missing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew Noakes</title>
		<link>http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411/comment-page-1#comment-21935</link>
		<dc:creator>Drew Noakes</dc:creator>
		<pubDate>Tue, 30 Jan 2007 14:48:16 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411#comment-21935</guid>
		<description>I&#039;d hoped that this would help me out, but as with Chris above, my conf file already has the CWD prepend, so I&#039;m stuck for now...</description>
		<content:encoded><![CDATA[<p>I&#8217;d hoped that this would help me out, but as with Chris above, my conf file already has the CWD prepend, so I&#8217;m stuck for now&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411/comment-page-1#comment-18219</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 04 Jan 2007 02:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411#comment-18219</guid>
		<description>Hmm, I got the same error but all my lighttpd.conf files already had “bin-path” =&gt; CWD + “/public/dispatch.fcgi”,</description>
		<content:encoded><![CDATA[<p>Hmm, I got the same error but all my lighttpd.conf files already had “bin-path” =&gt; CWD + “/public/dispatch.fcgi”,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Watson</title>
		<link>http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411/comment-page-1#comment-724</link>
		<dc:creator>Eric Watson</dc:creator>
		<pubDate>Mon, 08 May 2006 14:32:45 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411#comment-724</guid>
		<description>Wonderful...Thanks!</description>
		<content:encoded><![CDATA[<p>Wonderful&#8230;Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411/comment-page-1#comment-533</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sun, 16 Apr 2006 12:18:07 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411#comment-533</guid>
		<description>Rockin&#039;.  Just beat my head on exactly this issue for a couple of hours before hitting this.  thanks</description>
		<content:encoded><![CDATA[<p>Rockin&#8217;.  Just beat my head on exactly this issue for a couple of hours before hitting this.  thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Li</title>
		<link>http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411/comment-page-1#comment-453</link>
		<dc:creator>Li</dc:creator>
		<pubDate>Tue, 11 Apr 2006 07:29:38 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411#comment-453</guid>
		<description>worked for me too, though I only changed the config/lighttpd.conf on my web application because I can&#039;t find the first file you were talking about. Everything works fine! Thanks :)</description>
		<content:encoded><![CDATA[<p>worked for me too, though I only changed the config/lighttpd.conf on my web application because I can&#8217;t find the first file you were talking about. Everything works fine! Thanks <img src='http://gabrito.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan K.</title>
		<link>http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411/comment-page-1#comment-452</link>
		<dc:creator>Dan K.</dc:creator>
		<pubDate>Tue, 11 Apr 2006 06:20:21 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/issue-and-solution-for-upgrading-lighttpd-from-148-to-1411#comment-452</guid>
		<description>Indeed, someone did! Thanks for the hint!</description>
		<content:encoded><![CDATA[<p>Indeed, someone did! Thanks for the hint!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

