<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>All things Sysadmin</title>
	<link>http://northernmost.org/blog</link>
	<description>Just another manic Monday</description>
	<lastBuildDate>Wed, 26 May 2010 13:21:39 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.0" -->

	<item>
		<title>Legitimate emails being dropped by Spamassassin in RHEL5</title>
		<description><![CDATA[Over the past few months, an increasing number of customers have complained that their otherwise OK spam filters have started dropping an inordinate amount of legitimate emails. ]]></description>
		<link>http://northernmost.org/blog/legitimate-emails-being-dropped-by-spamassassin-in-rhel5/</link>
			</item>
	<item>
		<title>Control groups in RHEL6</title>
		<description><![CDATA[One new feature that I'm very enthusiastic about in RHEL6 is Control Groups (cgroup for short). It allows you to create groups and allocate resources to these. You can then bunch your applications into groups at your heart's content. ]]></description>
		<link>http://northernmost.org/blog/control-groups-in-rhel6/</link>
			</item>
	<item>
		<title>Boot loader not working in rhel6 beta under xen</title>
		<description><![CDATA[Just a heads up I thought I&#8217;d share in the hope that it&#8217;ll save someone some time, when installing RHEL6 beta under Xen, be aware that pygrub currently can&#8217;t handle /boot being on ext4 (which is the default). So in order to run rhel6 under xen, ensure that you modify the partition layout during the [...]]]></description>
		<link>http://northernmost.org/blog/boot-loader-not-installed-in-rhel6-beta/</link>
			</item>
	<item>
		<title>Building Hiphop PHP gotcha</title>
		<description><![CDATA[Tonight I've delved into the world of Facebook's HipHop for PHP. Unfortunately I set about this task on an RHEL 5.4 box, and it hasn't been a walk in the park. Quite a few dependencies were out of date or didn't exist in the repositories, libicu, boost, onig, tbb etc. Though, CMake did a good job of telling me what was wrong, so it wasn't a huge deal, I just compiled the missing pieces from source and put them in $CMAKE_PREFIX_PATH. One thing CMake didn't pick up on however, was that the flex version shipped with current RHEL is rather outdated.]]></description>
		<link>http://northernmost.org/blog/building-hiphop-php-gotcha/</link>
			</item>
	<item>
		<title>Development, just as important as dual NICs</title>
		<description><![CDATA[So after you've demanded dual power feeds to your rack, bonded NICs and a gazillion physical paths to your dual controller SAN, it would make sense to apply the same attitude towards your developers. After all, they are carbon based humans and are far more likely to break than your silicon NIC.]]></description>
		<link>http://northernmost.org/blog/development-just-as-important-as-dual-nics/</link>
			</item>
	<item>
		<title>GlusterFS tcp_nodelay patch update</title>
		<description><![CDATA[As mentioned in my previous post, I wrote a patch for GlusterFS to increase its performance when operating on many smaller files. Someone told me the other day that this functionality has been pushed to the git repository. ]]></description>
		<link>http://northernmost.org/blog/glusterfs-tcp_nodelay-patch-update/</link>
			</item>
	<item>
		<title>Improving GlusterFS performance</title>
		<description><![CDATA[Then I tried many frequent filesystem operations, untarring the 2.6.9 linux kernel from and onto the mount.  Not so brilliant! It took 23-24 minutes from start to finish. The 2.6.9 kernel contain 17477 files and the average size is just a few kilobytes. This is obviously a lot of smaller bursts of network traffic!]]></description>
		<link>http://northernmost.org/blog/improving-glusterfs-performance/</link>
			</item>
	<item>
		<title>Don&#8217;t fix, work around &#8211; MySQL</title>
		<description><![CDATA[Sun decided to not go down the route of reviewing and accepting the patches, but are now suggesting - are you sitting down? - running multiple instances on the same hardware. ]]></description>
		<link>http://northernmost.org/blog/dont-fix-work-around-mysql/</link>
			</item>
	<item>
		<title>Flush bash_history after each command</title>
		<description><![CDATA[If you, like me, often work in a lot of terminals on a lot of servers, or even a lot of terminals on the same one, you may recognise the frustration of a lost bash history. ]]></description>
		<link>http://northernmost.org/blog/flush-bash_history-after-each-command/</link>
			</item>
	<item>
		<title>Multiple backends with Varnish</title>
		<description><![CDATA[So as of now, you can safely use one varnish instance for several front-ends, thus eliminate double-caching (memory waste, unnecessary load on back-ends), reduce network traffic, do rudimentary load balancing, ease management etc.
With the obscene amount of traffic Varnish can push without putting a fairly basic system under any load worth mentioning, you can use a single front-end to serve several nodes in most setups.]]></description>
		<link>http://northernmost.org/blog/multiple-backends-with-varnish/</link>
			</item>
</channel>
</rss>
