<?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 on: mysql and disk space anomoloy</title>
	<atom:link href="http://alexlurthu.wordpress.com/2008/12/29/mysql-and-disk-space-anomoloy/feed/" rel="self" type="application/rss+xml" />
	<link>http://alexlurthu.wordpress.com/2008/12/29/mysql-and-disk-space-anomoloy/</link>
	<description>Straight from the heart!</description>
	<lastBuildDate>Thu, 17 Dec 2009 16:33:54 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kristian Nielsen</title>
		<link>http://alexlurthu.wordpress.com/2008/12/29/mysql-and-disk-space-anomoloy/#comment-167</link>
		<dc:creator>Kristian Nielsen</dc:creator>
		<pubDate>Mon, 29 Dec 2008 07:59:46 +0000</pubDate>
		<guid isPermaLink="false">http://alexlurthu.wordpress.com/?p=56#comment-167</guid>
		<description>It is not so much for security. But by deleting the file immediately, it is ensured
that the file will be removed by the operating system when it is closed, also if the
application should crash during processing the file. This avoids leaving temporary
files around on disk in case of crash.</description>
		<content:encoded><![CDATA[<p>It is not so much for security. But by deleting the file immediately, it is ensured<br />
that the file will be removed by the operating system when it is closed, also if the<br />
application should crash during processing the file. This avoids leaving temporary<br />
files around on disk in case of crash.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexlurthu.wordpress.com/2008/12/29/mysql-and-disk-space-anomoloy/#comment-166</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 29 Dec 2008 06:45:44 +0000</pubDate>
		<guid isPermaLink="false">http://alexlurthu.wordpress.com/?p=56#comment-166</guid>
		<description>Thanks Joshua for the interesting explanation.</description>
		<content:encoded><![CDATA[<p>Thanks Joshua for the interesting explanation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Kugler</title>
		<link>http://alexlurthu.wordpress.com/2008/12/29/mysql-and-disk-space-anomoloy/#comment-165</link>
		<dc:creator>Joshua Kugler</dc:creator>
		<pubDate>Mon, 29 Dec 2008 06:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://alexlurthu.wordpress.com/?p=56#comment-165</guid>
		<description>If I&#039;m understanding your post correctly, it makes perfect sense.  On a Unix system, to make your temp file the most secure you open it, then immediately delete it.  As long as it&#039;s open, you still have read/write access to the file, but no one else can open it since the file does not show up in the directory listing.

Thus, df would show the space loss because it looks at the block device.  du would not show it because it walks the tree to find its file size counts.</description>
		<content:encoded><![CDATA[<p>If I&#8217;m understanding your post correctly, it makes perfect sense.  On a Unix system, to make your temp file the most secure you open it, then immediately delete it.  As long as it&#8217;s open, you still have read/write access to the file, but no one else can open it since the file does not show up in the directory listing.</p>
<p>Thus, df would show the space loss because it looks at the block device.  du would not show it because it walks the tree to find its file size counts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
