<?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>All things Sysadmin &#187; Webservers</title>
	<atom:link href="http://northernmost.org/blog/category/all-things-webservers/feed/" rel="self" type="application/rss+xml" />
	<link>http://northernmost.org/blog</link>
	<description>Just another manic Monday</description>
	<lastBuildDate>Wed, 26 May 2010 13:21:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Building Hiphop PHP gotcha</title>
		<link>http://northernmost.org/blog/building-hiphop-php-gotcha/</link>
		<comments>http://northernmost.org/blog/building-hiphop-php-gotcha/#comments</comments>
		<pubDate>Sun, 21 Feb 2010 03:04:22 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[Sundry sysadmin]]></category>
		<category><![CDATA[Webservers]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=219</guid>
		<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>
		<wfw:commentRss>http://northernmost.org/blog/building-hiphop-php-gotcha/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Multiple backends with Varnish</title>
		<link>http://northernmost.org/blog/multiple-backends-with-varnish/</link>
		<comments>http://northernmost.org/blog/multiple-backends-with-varnish/#comments</comments>
		<pubDate>Mon, 15 Sep 2008 23:25:54 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[Webservers]]></category>
		<category><![CDATA[misc]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[load balancing]]></category>
		<category><![CDATA[varnish]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=123</guid>
		<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>
		<wfw:commentRss>http://northernmost.org/blog/multiple-backends-with-varnish/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</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>Erik Ljungstrom</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>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>mod_log_forensic howto</title>
		<link>http://northernmost.org/blog/mod_log_forensic-howto/</link>
		<comments>http://northernmost.org/blog/mod_log_forensic-howto/#comments</comments>
		<pubDate>Sun, 24 Feb 2008 01:21:06 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[Sundry sysadmin]]></category>
		<category><![CDATA[Webservers]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[mod_log_forensics]]></category>
		<category><![CDATA[mod_unique_id]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/mod_log_forensic-howto/</guid>
		<description><![CDATA[mod_log_forensic is an often forgotten yet very handy tool in debugging webservers. It gives each request a unique ID which you can then track through your log. It first writes the request prefixed with the unique ID, then it writes the same ID once the request is completed. Very useful to spot scripts which never [...]]]></description>
		<wfw:commentRss>http://northernmost.org/blog/mod_log_forensic-howto/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP 5.1 and 5.2 and MySQL 5.1.20+</title>
		<link>http://northernmost.org/blog/php-51-and-52-and-mysql-5120/</link>
		<comments>http://northernmost.org/blog/php-51-and-52-and-mysql-5120/#comments</comments>
		<pubDate>Fri, 22 Feb 2008 22:01:04 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[Webservers]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[compile errors]]></category>
		<category><![CDATA[gptr]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[mysqli]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/php-51-and-52-and-mysql-5120/</guid>
		<description><![CDATA[Today I fell victim of a gotcha when custom compiling PHP 5.1.4 for a customer which runs MySQL 5.1.22. The customer in question requires the mysqli component which appears to be broken with these versions (fixed in 5.2.4 though). So if you configure PHP with --with-mysqli=/usr/bin/mysql_config enabled you will soon find yourself staring at: /usr/local/src/php-5.1.4/ext/mysqli/mysqli_api.c: [...]]]></description>
		<wfw:commentRss>http://northernmost.org/blog/php-51-and-52-and-mysql-5120/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Hacked webapps</title>
		<link>http://northernmost.org/blog/hacked-webapps/</link>
		<comments>http://northernmost.org/blog/hacked-webapps/#comments</comments>
		<pubDate>Fri, 22 Feb 2008 01:27:22 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[Webservers]]></category>
		<category><![CDATA[joomla]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[script kiddies]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[webapps]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/hacked-webapps/</guid>
		<description><![CDATA[Disclaimer: I say ‘hack’ and ‘hacker’, both you jargon puritans out there and myself know they’re not. Really. But it’s a short and easy to spell word and with this disclaimer, everyone will know what I mean. Including the audience I mainly target with this post! This post might not be very relevant to the [...]]]></description>
		<wfw:commentRss>http://northernmost.org/blog/hacked-webapps/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Apache gotcha with ServerLimit</title>
		<link>http://northernmost.org/blog/apache-gotcha-with-serverlimit/</link>
		<comments>http://northernmost.org/blog/apache-gotcha-with-serverlimit/#comments</comments>
		<pubDate>Wed, 20 Feb 2008 04:20:13 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[Webservers]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[MaxClients]]></category>
		<category><![CDATA[ServerLimit]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/apache-gotcha-with-serverlimit/</guid>
		<description><![CDATA[A little gotcha that happened to me a while ago; A rather sizeable customer had just launched a new campaign and had problems with HTTP content matching alerts being thrown rather frequently. This particular solution has got five loadbalanced webservers and two database back-ends designed to cater for a reasonably high amount of traffic and [...]]]></description>
		<wfw:commentRss>http://northernmost.org/blog/apache-gotcha-with-serverlimit/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Highly unscientific comparison of webservers</title>
		<link>http://northernmost.org/blog/highly-unscientific-comparison-of-webservers/</link>
		<comments>http://northernmost.org/blog/highly-unscientific-comparison-of-webservers/#comments</comments>
		<pubDate>Wed, 20 Feb 2008 04:05:52 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[Sundry sysadmin]]></category>
		<category><![CDATA[Webservers]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[benchmark]]></category>
		<category><![CDATA[comparison]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[nginx]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/highly-unscientific-comparison-of-webservers/</guid>
		<description><![CDATA[A while ago a customer asked us to perform some benchmarks which would be applicable to their live application. The webservers in question are Apache, lighttpd and nginx The tests were made using apachebench on two dedicated machines with no other tasks and over a dedicated 100 mbit network. Some figures really surprises me/strikes me [...]]]></description>
		<wfw:commentRss>http://northernmost.org/blog/highly-unscientific-comparison-of-webservers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
