<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Neohexa &#187; Uncategorized</title>
	<atom:link href="http://neohexa.com/topics/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://neohexa.com</link>
	<description></description>
	<lastBuildDate>Mon, 14 Nov 2011 19:10:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Xen problems and the xen_emul_unplug argument</title>
		<link>http://neohexa.com/2011/09/xen-problems-and-the-xen_emul_unplug-argument/</link>
		<comments>http://neohexa.com/2011/09/xen-problems-and-the-xen_emul_unplug-argument/#comments</comments>
		<pubDate>Thu, 22 Sep 2011 03:38:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://neohexa.com/?p=134</guid>
		<description><![CDATA[Having spent a good amount of time working with the Xen platform, I&#8217;ve come across numerous occasions where the guest operating system would sometimes not detect disks and/or networking would not function. If you are having problems with a Linux based Xen guest, try this as a kernel argument at boot time: xen_emul_unplug=never I&#8217;ve used [...]]]></description>
			<content:encoded><![CDATA[<p>Having spent a good amount of time working with the Xen platform, I&#8217;ve come across numerous occasions where the guest operating system would sometimes not detect disks and/or networking would not function. If you are having problems with a Linux based Xen guest, try this as a kernel argument at boot time:</p>
<p><code>xen_emul_unplug=never</code></p>
<p>I&#8217;ve used it with success on Fedora, Ubuntu, and Debian personally.</p>
]]></content:encoded>
			<wfw:commentRss>http://neohexa.com/2011/09/xen-problems-and-the-xen_emul_unplug-argument/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quickly delete all e-mails in Exim queue</title>
		<link>http://neohexa.com/2011/09/quickly-delete-all-e-mails-in-exim-queue/</link>
		<comments>http://neohexa.com/2011/09/quickly-delete-all-e-mails-in-exim-queue/#comments</comments>
		<pubDate>Thu, 22 Sep 2011 03:29:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://neohexa.com/?p=132</guid>
		<description><![CDATA[If for some reason or another you end up with a ton of e-mails in the queue and need them gone quickly, the command below will do the trick: find /var/spool/exim/input -name '*.*' -exec rm {} \;]]></description>
			<content:encoded><![CDATA[<p>If for some reason or another you end up with a ton of e-mails in the queue and need them gone quickly, the command below will do the trick:</p>
<p><code>find /var/spool/exim/input -name '*.*' -exec rm {} \;</code></p>
]]></content:encoded>
			<wfw:commentRss>http://neohexa.com/2011/09/quickly-delete-all-e-mails-in-exim-queue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Speed up disk I/O with relatime option</title>
		<link>http://neohexa.com/2011/09/speed-up-disk-io-with-relatime-option/</link>
		<comments>http://neohexa.com/2011/09/speed-up-disk-io-with-relatime-option/#comments</comments>
		<pubDate>Thu, 22 Sep 2011 00:45:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://neohexa.com/?p=118</guid>
		<description><![CDATA[Most distros are now using ext4, which is great. We know that ext4 performs better than ext3. Did you know that you can make your system perform even better with a thirty second file modification? The &#8220;relatime&#8221; option controls how ext4 records last access time information for files. By default, ext4 will modify a timestamp [...]]]></description>
			<content:encoded><![CDATA[<p>Most distros are now using ext4, which is great. We know that ext4 performs better than ext3. Did you know that you can make your system perform even better with a thirty second file modification?</p>
<p>The &#8220;relatime&#8221; option controls how ext4 records last access time information for files. By default, ext4 will modify a timestamp on a file everytime it is accessed. This may not seem like a significant performance killer, but trust me, it is. Adding relatime stops this from occurring, boosting your performance.</p>
<p>Your /etc/fstab file will looking something like this:</p>
<p><code># /etc/fstab: static file system information.<br />
#<br />
# Use 'blkid -o value -s UUID' to print the universally unique identifier<br />
# for a device; this may be used with UUID= as a more robust way to name<br />
# devices that works even if disks are added and removed. See fstab(5).<br />
#<br />
# <file system> <mount point>   <type><br />
<options>       <dump>
<pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0<br />
/dev/sda3       /               ext4    errors=remount-ro 0       1<br />
# /boot was on /dev/sda1 during installation<br />
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /boot           ext3    defaults        0       2<br />
# /home was on /dev/sda4 during installation<br />
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /home           ext4    defaults        0       2<br />
# swap was on /dev/sda2 during installation<br />
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx none            swap    sw              0       0<br />
# ramdisk<br />
tmpfs		/tmp/ramdisk	tmpfs	rw,size=2G	0	0</code></p>
<p>We want to add the &#8220;relatime&#8221; option to your &#8220;/&#8221; partition. Also, your &#8220;/home&#8221; partition, if you have a separate &#8220;/home&#8221;. When done, your /etc/fstab will look more like this:</p>
<p><code># /etc/fstab: static file system information.<br />
#<br />
# Use 'blkid -o value -s UUID' to print the universally unique identifier<br />
# for a device; this may be used with UUID= as a more robust way to name<br />
# devices that works even if disks are added and removed. See fstab(5).<br />
#<br />
# <file system> <mount point>   <type><br />
<options>       <dump>
<pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0<br />
/dev/sda3       /               ext4    <strong>relatime</strong>,errors=remount-ro 0       1<br />
# /boot was on /dev/sda1 during installation<br />
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /boot           ext3    defaults        0       2<br />
# /home was on /dev/sda4 during installation<br />
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /home           ext4    <strong>relatime</strong>,defaults        0       2<br />
# swap was on /dev/sda2 during installation<br />
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx none            swap    sw              0       0<br />
# ramdisk<br />
tmpfs		/tmp/ramdisk	tmpfs	rw,size=2G	0	0</code></p>
<p>Now, most would say to reboot your computer to have the change take effect. Not necessary. Simply run:</p>
<p><code>sudo mount -o remount /<br />
sudo mount -o remount /home (if you have a separate /home)</code></p>
<p>Enjoy your speedier installation.</p>
]]></content:encoded>
			<wfw:commentRss>http://neohexa.com/2011/09/speed-up-disk-io-with-relatime-option/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exim DB Problem</title>
		<link>http://neohexa.com/2010/10/exim-db-problem/</link>
		<comments>http://neohexa.com/2010/10/exim-db-problem/#comments</comments>
		<pubDate>Tue, 05 Oct 2010 14:32:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://neohexa.com/?p=112</guid>
		<description><![CDATA[If you find that incoming mail is rejected by Exim, and you see the following in your logfile, move /var/spool/exim/db/ratelimit out of the way, and then restart Exim. Problem solved. failed to open DB file /var/spool/exim/db/ratelimit: Bad file descriptor Berkeley DB error: memp_fopen: page sizes must be a power-of-2]]></description>
			<content:encoded><![CDATA[<p>If you find that incoming mail is rejected by Exim, and you see the following in your logfile, move /var/spool/exim/db/ratelimit out of the way, and then restart Exim. Problem solved.</p>
<p><code>failed to open DB file /var/spool/exim/db/ratelimit: Bad file descriptor<br />
Berkeley DB error: memp_fopen: page sizes must be a power-of-2</code></p>
]]></content:encoded>
			<wfw:commentRss>http://neohexa.com/2010/10/exim-db-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

