<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Trinity's World</title>
	<atom:link href="http://trinity777.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://trinity777.wordpress.com</link>
	<description>Enter at own risk</description>
	<lastBuildDate>Fri, 30 Oct 2009 23:08:23 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on WordPress 2.6: The issue of &#8220;wp-cron.php&#8221; by Bryant</title>
		<link>http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/#comment-4353</link>
		<dc:creator>Bryant</dc:creator>
		<pubDate>Fri, 30 Oct 2009 23:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=340#comment-4353</guid>
		<description>I struggled with this for a long time. I received next to no support from my hosting company (inmotion) and about as little from the Wordpress forums. In the end, after trying the above mention solution, I still had similar problems. I dumped inmotion and took my blog to Bluehost. In the several weeks since I have been there I have had no problems at all and am not forced to use some kind of workaround. I am more convinced than ever that the hosting configuration makes all the difference.

That said, Wordpress ought to deal with this as it is a long running, unnecessary problem.</description>
		<content:encoded><![CDATA[<p>I struggled with this for a long time. I received next to no support from my hosting company (inmotion) and about as little from the WordPress forums. In the end, after trying the above mention solution, I still had similar problems. I dumped inmotion and took my blog to Bluehost. In the several weeks since I have been there I have had no problems at all and am not forced to use some kind of workaround. I am more convinced than ever that the hosting configuration makes all the difference.</p>
<p>That said, WordPress ought to deal with this as it is a long running, unnecessary problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress 2.6: The issue of &#8220;wp-cron.php&#8221; by Aaron</title>
		<link>http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/#comment-4352</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 30 Oct 2009 22:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=340#comment-4352</guid>
		<description>Also running 2.8.5.  Interested in what is discussed with Dave, above.</description>
		<content:encoded><![CDATA[<p>Also running 2.8.5.  Interested in what is discussed with Dave, above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress 2.6: The issue of &#8220;wp-cron.php&#8221; by Dave Schuler</title>
		<link>http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/#comment-4351</link>
		<dc:creator>Dave Schuler</dc:creator>
		<pubDate>Fri, 30 Oct 2009 00:17:58 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=340#comment-4351</guid>
		<description>trinity777:

Can you contact me at the email address I&#039;ve provided?  I&#039;ve run into the problem you describe but I&#039;ve run into it with Wordpress 2.8.5 and your prescription above doesn&#039;t seem to apply.

I hate to bug you but I&#039;ve left requests on the WP forums and received no responses.  You seem to have thought about this a bit so, if possible, I&#039;d like to bat it around with you.</description>
		<content:encoded><![CDATA[<p>trinity777:</p>
<p>Can you contact me at the email address I&#8217;ve provided?  I&#8217;ve run into the problem you describe but I&#8217;ve run into it with WordPress 2.8.5 and your prescription above doesn&#8217;t seem to apply.</p>
<p>I hate to bug you but I&#8217;ve left requests on the WP forums and received no responses.  You seem to have thought about this a bit so, if possible, I&#8217;d like to bat it around with you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress 2.6: The issue of &#8220;wp-cron.php&#8221; by rvegas</title>
		<link>http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/#comment-4349</link>
		<dc:creator>rvegas</dc:creator>
		<pubDate>Tue, 22 Sep 2009 17:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=340#comment-4349</guid>
		<description>This line is not included in WP 2.8.3. How do I apply this same solution to 2.8.3? Or how do I make wp-cron run only when I hit the wp-cron.php file with a web browser event. Thanks!</description>
		<content:encoded><![CDATA[<p>This line is not included in WP 2.8.3. How do I apply this same solution to 2.8.3? Or how do I make wp-cron run only when I hit the wp-cron.php file with a web browser event. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress 2.6: The issue of &#8220;wp-cron.php&#8221; by wordpressUser</title>
		<link>http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/#comment-4348</link>
		<dc:creator>wordpressUser</dc:creator>
		<pubDate>Sat, 19 Sep 2009 04:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=340#comment-4348</guid>
		<description>you really don&#039;t want to be hitting the database for every page hit either... storing data in memory cache is much much faster than going to the db every time (executing sql is more cpu intensive then fetching data from memory)... you want a dynamic site, you have to pay the price somewhere.</description>
		<content:encoded><![CDATA[<p>you really don&#8217;t want to be hitting the database for every page hit either&#8230; storing data in memory cache is much much faster than going to the db every time (executing sql is more cpu intensive then fetching data from memory)&#8230; you want a dynamic site, you have to pay the price somewhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Filtering: Should Google be Involved in the Splog Battle by sandrar</title>
		<link>http://trinity777.wordpress.com/2008/07/16/content-filtering-should-google-be-involved-in-the-splog-battle/#comment-4347</link>
		<dc:creator>sandrar</dc:creator>
		<pubDate>Thu, 10 Sep 2009 19:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=222#comment-4347</guid>
		<description>Hi! I was surfing and found your blog post... nice! I love your blog.  :) Cheers! Sandra. R.</description>
		<content:encoded><![CDATA[<p>Hi! I was surfing and found your blog post&#8230; nice! I love your blog.  <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Cheers! Sandra. R.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress 2.6: The issue of &#8220;wp-cron.php&#8221; by evcthosting</title>
		<link>http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/#comment-4346</link>
		<dc:creator>evcthosting</dc:creator>
		<pubDate>Thu, 03 Sep 2009 04:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=340#comment-4346</guid>
		<description>Just to pipe in on the host side, my guys had one hell of time tracking this wp-cron.php issue down. what we mistook for several different types of attempted attacks was this little guy bloating up our Apache server (that makes the websites work) and our MySQL server as well. I too had to send that horrid suspended notice out. We had no choice to to do so because it stole the entire server and took it over. not really but none of our customers on that server could access it. its sad that they have not fixed it yet because we love to support the software but not at the cost of my techs sanity and the customers pocket book. After finding the link above and one from cPanel we were able to find a solution to what &quot;our&quot; issue was as the provider and be able to un-suspend our happy customers. now if Word press can find it in their hearts to add this fix to the next version maybe the hosters out there can stop having to suspend peoples service for using software that everyone wants to use. GRRR. 

cheers!!</description>
		<content:encoded><![CDATA[<p>Just to pipe in on the host side, my guys had one hell of time tracking this wp-cron.php issue down. what we mistook for several different types of attempted attacks was this little guy bloating up our Apache server (that makes the websites work) and our MySQL server as well. I too had to send that horrid suspended notice out. We had no choice to to do so because it stole the entire server and took it over. not really but none of our customers on that server could access it. its sad that they have not fixed it yet because we love to support the software but not at the cost of my techs sanity and the customers pocket book. After finding the link above and one from cPanel we were able to find a solution to what &#8220;our&#8221; issue was as the provider and be able to un-suspend our happy customers. now if Word press can find it in their hearts to add this fix to the next version maybe the hosters out there can stop having to suspend peoples service for using software that everyone wants to use. GRRR. </p>
<p>cheers!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress 2.6: The issue of &#8220;wp-cron.php&#8221; by cron job &#124; Mārtiņa Štāla blogs</title>
		<link>http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/#comment-4345</link>
		<dc:creator>cron job &#124; Mārtiņa Štāla blogs</dc:creator>
		<pubDate>Wed, 05 Aug 2009 05:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=340#comment-4345</guid>
		<description>[...] http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/    Tēmas:Beztēma Birkas:        Komentāri (0) Atsaišu sūtīšana (0) Komentēt Atsaite [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/" rel="nofollow">http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/</a>    Tēmas:Beztēma Birkas:        Komentāri (0) Atsaišu sūtīšana (0) Komentēt Atsaite [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Somthing to Show For It by Mom</title>
		<link>http://trinity777.wordpress.com/2009/07/22/somthing-to-show-for-it/#comment-4344</link>
		<dc:creator>Mom</dc:creator>
		<pubDate>Thu, 30 Jul 2009 00:23:13 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=432#comment-4344</guid>
		<description>You sure live in a beautiful area.  Thanks for posting the picts.</description>
		<content:encoded><![CDATA[<p>You sure live in a beautiful area.  Thanks for posting the picts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress 2.6: The issue of &#8220;wp-cron.php&#8221; by trinity777</title>
		<link>http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/#comment-4342</link>
		<dc:creator>trinity777</dc:creator>
		<pubDate>Tue, 09 Jun 2009 10:40:40 +0000</pubDate>
		<guid isPermaLink="false">http://trinity777.wordpress.com/?p=340#comment-4342</guid>
		<description>jbevans, that is great!  I like the touch of having your server e-mail you so you know exactly when wp-cron is hit without searching a log.  Technology put to good use!</description>
		<content:encoded><![CDATA[<p>jbevans, that is great!  I like the touch of having your server e-mail you so you know exactly when wp-cron is hit without searching a log.  Technology put to good use!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
