<?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: Redis will not time out. Try installing the SystemTimer gem.</title>
	<atom:link href="http://www.wetware.co.nz/2010/07/redis-will-not-time-out-try-installing-the-systemtimer-gem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wetware.co.nz/2010/07/redis-will-not-time-out-try-installing-the-systemtimer-gem/</link>
	<description>Getting computers to do stuff so we don&#039;t have too</description>
	<lastBuildDate>Tue, 17 Jan 2012 22:29:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jordan Carter</title>
		<link>http://www.wetware.co.nz/2010/07/redis-will-not-time-out-try-installing-the-systemtimer-gem/comment-page-1/#comment-3313</link>
		<dc:creator>Jordan Carter</dc:creator>
		<pubDate>Tue, 03 Aug 2010 22:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=752#comment-3313</guid>
		<description>I found that I had the wrong version of the gems.
Once that was fixed I noticed that I had followed the instructions on github and setup a redis config/init script which held environment specific configurations.  I then noticed that I didn&#039;t have an environment config for development, which is why it was throwing the error.  Would have been nice for it to throw a different error tho.</description>
		<content:encoded><![CDATA[<p>I found that I had the wrong version of the gems.<br />
Once that was fixed I noticed that I had followed the instructions on github and setup a redis config/init script which held environment specific configurations.  I then noticed that I didn&#8217;t have an environment config for development, which is why it was throwing the error.  Would have been nice for it to throw a different error tho.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Petr Kaleta</title>
		<link>http://www.wetware.co.nz/2010/07/redis-will-not-time-out-try-installing-the-systemtimer-gem/comment-page-1/#comment-3301</link>
		<dc:creator>Petr Kaleta</dc:creator>
		<pubDate>Tue, 27 Jul 2010 08:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=752#comment-3301</guid>
		<description>I got exactly the same problem, after running each rake task it says &quot;WARNING: Could not find a good alternative for performing time outs -- connecting to Redis will not time out. Try installing the SystemTimer gem.
&quot; but no error after that.

system_timer is installed on my machine. All gems are updated.

Any suggestion?</description>
		<content:encoded><![CDATA[<p>I got exactly the same problem, after running each rake task it says &#8220;WARNING: Could not find a good alternative for performing time outs &#8212; connecting to Redis will not time out. Try installing the SystemTimer gem.<br />
&#8221; but no error after that.</p>
<p>system_timer is installed on my machine. All gems are updated.</p>
<p>Any suggestion?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

