<?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"
	>

<channel>
	<title>All things Sysadmin</title>
	<atom:link href="http://northernmost.org/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://northernmost.org/blog</link>
	<description>Just another manic Monday</description>
	<pubDate>Tue, 26 Aug 2008 21:49:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<item>
		<title>tooltip - inotify-tools</title>
		<link>http://northernmost.org/blog/tooltip-inotify-tools/</link>
		<comments>http://northernmost.org/blog/tooltip-inotify-tools/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 21:49:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[misc]]></category>

		<category><![CDATA[I/O utilization]]></category>

		<category><![CDATA[inotify]]></category>

		<category><![CDATA[inotify-tools]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=47</guid>
		<description><![CDATA[You can monitor pretty much any file operation, so this tool can be used in a whole range of scenarios. Ever wondered just how many temp files your application creates or? Are you sure it doesn't open and close the file handle for each operation? Do you want to know which file on your website is the most popular download at the moment but can't wait until the webstats crontab has ran? I could go on...]]></description>
		<wfw:commentRss>http://northernmost.org/blog/tooltip-inotify-tools/feed/</wfw:commentRss>
		</item>
		<item>
		<title>lighttpd 2.0</title>
		<link>http://northernmost.org/blog/lighttpd-20/</link>
		<comments>http://northernmost.org/blog/lighttpd-20/#comments</comments>
		<pubDate>Sat, 02 Aug 2008 23:41:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Webservers]]></category>

		<category><![CDATA[lighttpd]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=35</guid>
		<description><![CDATA[While I've experienced some of the "oddities" they refer to, I have every bit of confidence in the developers. Even so - it's a risky path to go down. They will most likely iron out the current shortcomings and oddities, but it's fairly likely that a few new will be introduced during the course of rewriting. 
]]></description>
		<wfw:commentRss>http://northernmost.org/blog/lighttpd-20/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Some trickery or resilience with Varnish</title>
		<link>http://northernmost.org/blog/some-trickery-or-resilience-with-varnish/</link>
		<comments>http://northernmost.org/blog/some-trickery-or-resilience-with-varnish/#comments</comments>
		<pubDate>Tue, 22 Jul 2008 00:56:11 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Sundry sysadmin]]></category>

		<category><![CDATA[resilience]]></category>

		<category><![CDATA[restart]]></category>

		<category><![CDATA[varnish]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=33</guid>
		<description><![CDATA[If you've got two or more backends, and under some condition can't or won't serve a request immediately or want to send it elsewhere depending on some circumstance, you can do this using HTTP return code or header with the not-so-well-documented feature 'restart' ]]></description>
		<wfw:commentRss>http://northernmost.org/blog/some-trickery-or-resilience-with-varnish/feed/</wfw:commentRss>
		</item>
		<item>
		<title>LVM with dmraid</title>
		<link>http://northernmost.org/blog/lvm-with-dmraid/</link>
		<comments>http://northernmost.org/blog/lvm-with-dmraid/#comments</comments>
		<pubDate>Tue, 15 Jul 2008 21:05:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Sundry sysadmin]]></category>

		<category><![CDATA[dmraid]]></category>

		<category><![CDATA[lvm]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=32</guid>
		<description><![CDATA[hen adding a new disk for a customer running CentOS 4.7 on severely old hardware, I bumped into something I've never had happening to me before. Basically the system wouldn't let me create the Physical Volume]]></description>
		<wfw:commentRss>http://northernmost.org/blog/lvm-with-dmraid/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Resyncing slaves with slaves</title>
		<link>http://northernmost.org/blog/resyncing-slaves-with-slaves/</link>
		<comments>http://northernmost.org/blog/resyncing-slaves-with-slaves/#comments</comments>
		<pubDate>Sat, 05 Jul 2008 02:44:17 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<category><![CDATA[replication]]></category>

		<category><![CDATA[resync slave]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=31</guid>
		<description><![CDATA[When dealing with replicated setups with two or more slaves sharing a master, it appears as if a lot of people overlook the obvious. You don't need to take your master down to resync a slave. I was hoping I wouldn't need to post about this, but I see people taking down their masters when they have perfectly healthy slaves way too often to let it slip. 
]]></description>
		<wfw:commentRss>http://northernmost.org/blog/resyncing-slaves-with-slaves/feed/</wfw:commentRss>
		</item>
		<item>
		<title>MySQL load balancing with mylbhelper</title>
		<link>http://northernmost.org/blog/mysql-load-balancing-with-mylbhelper/</link>
		<comments>http://northernmost.org/blog/mysql-load-balancing-with-mylbhelper/#comments</comments>
		<pubDate>Sun, 29 Jun 2008 02:59:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<category><![CDATA[Sundry sysadmin]]></category>

		<category><![CDATA[hardware load balancing]]></category>

		<category><![CDATA[mylbhelper]]></category>

		<category><![CDATA[mysql load balancing]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=30</guid>
		<description><![CDATA[A customer of ours was in this particular situation. They had a very decent hardware load balancer for their webservers with capacity to spare. So they ended up load balancing the mysql instances through the same device and using a piece of software I've written called <a href="http://mylbhelper.northernmost.org">mylbhelper</a>. 
]]></description>
		<wfw:commentRss>http://northernmost.org/blog/mysql-load-balancing-with-mylbhelper/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Tool tip: mysqlsniffer</title>
		<link>http://northernmost.org/blog/tool-tip-mysqlsniff/</link>
		<comments>http://northernmost.org/blog/tool-tip-mysqlsniff/#comments</comments>
		<pubDate>Wed, 18 Jun 2008 23:59:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<category><![CDATA[mysqlsniff]]></category>

		<category><![CDATA[querysniffer]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=29</guid>
		<description><![CDATA[mysqlsniff is a tool that I find very useful and utilise a lot, but it doesn't seem to be so widely known as it deserves to be. It's pretty much general_log light without a restart!]]></description>
		<wfw:commentRss>http://northernmost.org/blog/tool-tip-mysqlsniff/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Wet dream finally coming through?</title>
		<link>http://northernmost.org/blog/wet-dream-finally-coming-through/</link>
		<comments>http://northernmost.org/blog/wet-dream-finally-coming-through/#comments</comments>
		<pubDate>Tue, 03 Jun 2008 22:17:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<category><![CDATA[maatkit]]></category>

		<category><![CDATA[mysql]]></category>

		<category><![CDATA[self healing replication]]></category>

		<category><![CDATA[summer of code]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=28</guid>
		<description><![CDATA[My major beef with it is that it's not self-healing. Sure, you can monitor, script and re-jig things to a certain extent. But this is why I was thrilled when read the MySQL Forge suggestions for Google Summer of Code. One of the suggestions is to enable self-healing replication using components, or at least concepts, from maatkit and Google's MMRM.  ]]></description>
		<wfw:commentRss>http://northernmost.org/blog/wet-dream-finally-coming-through/feed/</wfw:commentRss>
		</item>
		<item>
		<title>paramy - import dumps in a flash</title>
		<link>http://northernmost.org/blog/paramy-import-dumps-in-a-flash/</link>
		<comments>http://northernmost.org/blog/paramy-import-dumps-in-a-flash/#comments</comments>
		<pubDate>Fri, 30 May 2008 21:35:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<category><![CDATA[data import]]></category>

		<category><![CDATA[mysql]]></category>

		<category><![CDATA[paramy]]></category>

		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=27</guid>
		<description><![CDATA[Basically it's a multithreaded client. Most servers these days have, or certainly should have, multiple disks and multiple CPU cores and reasonably fast storage. So using a single threaded client to insert those hundreds of thousands or millions of records doesn't make that much sense today. There's quite a lot of time to save. I've ran some tests on MySQL 5.1.24 and compared the results with those from the stock mysql client.

]]></description>
		<wfw:commentRss>http://northernmost.org/blog/paramy-import-dumps-in-a-flash/feed/</wfw:commentRss>
		</item>
		<item>
		<title>InnoDB plugin compression with benchmarks</title>
		<link>http://northernmost.org/blog/innodb-plugin-compression-with-benchmarks/</link>
		<comments>http://northernmost.org/blog/innodb-plugin-compression-with-benchmarks/#comments</comments>
		<pubDate>Thu, 29 May 2008 19:57:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=26</guid>
		<description><![CDATA[InnoDB Plugin compression levels and their performance examined.]]></description>
		<wfw:commentRss>http://northernmost.org/blog/innodb-plugin-compression-with-benchmarks/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
