<?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: Cron Ignoring Changes in /etc/cron.d</title>
	<atom:link href="http://www.andyblyler.com/blog/2007/01/04/cron-ignoring-changes-in-etccrond/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.andyblyler.com/blog/2007/01/04/cron-ignoring-changes-in-etccrond/</link>
	<description>programmer / sys admin at Barracuda &#38; Nutshell, musician, soloing student pilot</description>
	<lastBuildDate>Tue, 27 Dec 2011 04:36:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brandon Craig Rhodes</title>
		<link>http://www.andyblyler.com/blog/2007/01/04/cron-ignoring-changes-in-etccrond/comment-page-1/#comment-31789</link>
		<dc:creator>Brandon Craig Rhodes</dc:creator>
		<pubDate>Tue, 27 Dec 2011 04:36:23 +0000</pubDate>
		<guid isPermaLink="false">http://beta.andyblyler.com/blog/2007/01/04/cron-ignoring-changes-in-etccrond/#comment-31789</guid>
		<description>&lt;p&gt;Thanks so much for this pointer — it helped me get my cron jobs running again! Oddly enough, cron my my modern (late-2011) Ubuntu install will notice a file-only change in mtime if the previous version of the crontab was valid; but if the crontab gets a syntax error or an invalid username in it and gets rejected, then only a directory mtime modification makes cron start paying attention to the file again.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks so much for this pointer — it helped me get my cron jobs running again! Oddly enough, cron my my modern (late-2011) Ubuntu install will notice a file-only change in mtime if the previous version of the crontab was valid; but if the crontab gets a syntax error or an invalid username in it and gets rejected, then only a directory mtime modification makes cron start paying attention to the file again.</p>]]></content:encoded>
	</item>
</channel>
</rss>

