<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for xadec.com</title>
	<link>http://www.xadec.com</link>
	<description>Test text</description>
	<pubDate>Wed, 07 Jan 2009 11:58:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>Comment on How to force only one Unix Perl, Python or Ruby script to be running at a time. by paranoid</title>
		<link>http://www.xadec.com/2007/06/09/how-to-force-only-one-unix-perl-python-or-ruby-script-to-be-running-at-a-time/#comment-5</link>
		<author>paranoid</author>
		<pubDate>Wed, 25 Jul 2007 20:05:07 +0000</pubDate>
		<guid>http://www.xadec.com/2007/06/09/how-to-force-only-one-unix-perl-python-or-ruby-script-to-be-running-at-a-time/#comment-5</guid>
					<description>I would be careful with this solution if scripts reside on NFS filesystems. Fcntl lock is not supported by all nfs implementations. More generic and safe solution would be to create scriptname.lock file manually.</description>
		<content:encoded><![CDATA[<p>I would be careful with this solution if scripts reside on NFS filesystems. Fcntl lock is not supported by all nfs implementations. More generic and safe solution would be to create scriptname.lock file manually.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
