<?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: suPHP + Userdir on Ubuntu</title>
	<atom:link href="http://www.rickogden.com/2010/01/suphp-userdir-on-ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rickogden.com/2010/01/suphp-userdir-on-ubuntu/</link>
	<description></description>
	<lastBuildDate>Thu, 22 Jul 2010 07:23:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Darren Nolan</title>
		<link>http://www.rickogden.com/2010/01/suphp-userdir-on-ubuntu/comment-page-1/#comment-175</link>
		<dc:creator>Darren Nolan</dc:creator>
		<pubDate>Sun, 04 Jul 2010 23:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.rickogden.com/?p=214#comment-175</guid>
		<description>with the way Rick has edited the suPHP configuration file, it&#039;s important to keep file and directory permissions correct.  One of the features I love about SuPHP is that (as it stands in the default config) all directories must be no higher than 755, and all files must be no higher than 644.

On production systems you&#039;re forcing users to keep their permissions closed to themselves and not open like a typical mod-php setup.

Incorrect File permissions will present a Internal Server Error 500.

But when in doubt, check your log file (example: /var/log/apache2/error.log) - =D

PS Love your work Rick.</description>
		<content:encoded><![CDATA[<p>with the way Rick has edited the suPHP configuration file, it&#8217;s important to keep file and directory permissions correct.  One of the features I love about SuPHP is that (as it stands in the default config) all directories must be no higher than 755, and all files must be no higher than 644.</p>
<p>On production systems you&#8217;re forcing users to keep their permissions closed to themselves and not open like a typical mod-php setup.</p>
<p>Incorrect File permissions will present a Internal Server Error 500.</p>
<p>But when in doubt, check your log file (example: /var/log/apache2/error.log) &#8211; =D</p>
<p>PS Love your work Rick.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Ogden</title>
		<link>http://www.rickogden.com/2010/01/suphp-userdir-on-ubuntu/comment-page-1/#comment-170</link>
		<dc:creator>Rick Ogden</dc:creator>
		<pubDate>Tue, 22 Jun 2010 09:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.rickogden.com/?p=214#comment-170</guid>
		<description>In which case check that you&#039;ve edited the config files correctly, as a syntax error in them is likely to cause these sorts of error messages.</description>
		<content:encoded><![CDATA[<p>In which case check that you&#8217;ve edited the config files correctly, as a syntax error in them is likely to cause these sorts of error messages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fulin</title>
		<link>http://www.rickogden.com/2010/01/suphp-userdir-on-ubuntu/comment-page-1/#comment-169</link>
		<dc:creator>fulin</dc:creator>
		<pubDate>Fri, 18 Jun 2010 09:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.rickogden.com/?p=214#comment-169</guid>
		<description>Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Apache/2.2.12 (Ubuntu) Server at 163.26.97.112 Port 80</description>
		<content:encoded><![CDATA[<p>Internal Server Error</p>
<p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p>
<p>Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p>
<p>More information about this error may be available in the server error log.</p>
<p>Apache/2.2.12 (Ubuntu) Server at 163.26.97.112 Port 80</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Ogden</title>
		<link>http://www.rickogden.com/2010/01/suphp-userdir-on-ubuntu/comment-page-1/#comment-166</link>
		<dc:creator>Rick Ogden</dc:creator>
		<pubDate>Wed, 16 Jun 2010 14:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.rickogden.com/?p=214#comment-166</guid>
		<description>What happens if you re-enable php5 (sudo a2enmod php5)?</description>
		<content:encoded><![CDATA[<p>What happens if you re-enable php5 (sudo a2enmod php5)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fulin</title>
		<link>http://www.rickogden.com/2010/01/suphp-userdir-on-ubuntu/comment-page-1/#comment-165</link>
		<dc:creator>fulin</dc:creator>
		<pubDate>Wed, 16 Jun 2010 12:54:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.rickogden.com/?p=214#comment-165</guid>
		<description>I execute &#039;sudo a2dismod php5&#039; command and restart apache2,but web server cannot run</description>
		<content:encoded><![CDATA[<p>I execute &#8217;sudo a2dismod php5&#8242; command and restart apache2,but web server cannot run</p>
]]></content:encoded>
	</item>
</channel>
</rss>
