<?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>UNIXy &#187; litespeed</title>
	<atom:link href="http://blog.unixy.net/tag/litespeed/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.unixy.net</link>
	<description>Truly Fully Managed Servers</description>
	<lastBuildDate>Thu, 29 Jul 2010 13:13:11 +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>Note that the MySQL client library is not bundled anymore. Solved!</title>
		<link>http://blog.unixy.net/2010/01/note-that-the-mysql-client-library-is-not-bundled-anymore-solved/</link>
		<comments>http://blog.unixy.net/2010/01/note-that-the-mysql-client-library-is-not-bundled-anymore-solved/#comments</comments>
		<pubDate>Sun, 31 Jan 2010 03:09:14 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Break-Fix]]></category>
		<category><![CDATA[build]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[lib64]]></category>
		<category><![CDATA[lightspeed]]></category>
		<category><![CDATA[litespeed]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://blog.unixy.net/?p=232</guid>
		<description><![CDATA[This error is not specific to Litespeed but can be encountered while building PHP with MySQL support on 64-bit systems. The fix is to tell the build that the MySQL client is indeed installed, but in a different directory, by adding the following flag to the configure line in Litespeed: --with-libdir=lib64 The reason being the [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fblog.unixy.net%2F2010%2F01%2Fnote-that-the-mysql-client-library-is-not-bundled-anymore-solved%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fblog.unixy.net%2F2010%2F01%2Fnote-that-the-mysql-client-library-is-not-bundled-anymore-solved%2F&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>This error is not specific to Litespeed but can be encountered while building PHP with MySQL support on 64-bit systems. The fix is to tell the build that the MySQL client is indeed installed, but in a different directory, by adding the following flag to the configure line in Litespeed:</p>
<blockquote><p><code>--with-libdir=lib64</code></p></blockquote>
<p>The reason being the build doesn&#8217;t know at this point that it is dealing with a 64-bit OS. If adding the above switch does not work, be sure to install the MySQL client and libraries.</p>
<p>That&#8217;s all folks!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.unixy.net/2010/01/note-that-the-mysql-client-library-is-not-bundled-anymore-solved/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Running vBulletin Cluster Using Varnish</title>
		<link>http://blog.unixy.net/2009/11/running-vbulletin-along-with-varnish/</link>
		<comments>http://blog.unixy.net/2009/11/running-vbulletin-along-with-varnish/#comments</comments>
		<pubDate>Sun, 29 Nov 2009 15:38:30 +0000</pubDate>
		<dc:creator>UNIXy</dc:creator>
				<category><![CDATA[Crash Course]]></category>
		<category><![CDATA[accelerator]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[cluster]]></category>
		<category><![CDATA[failover]]></category>
		<category><![CDATA[litespeed]]></category>
		<category><![CDATA[load balance]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[varnish]]></category>
		<category><![CDATA[vb]]></category>
		<category><![CDATA[vBulletin]]></category>
		<category><![CDATA[Xen]]></category>

		<guid isPermaLink="false">http://blog.unixy.net/?p=120</guid>
		<description><![CDATA[Varnish is an excellent Web accelerator that can be made to proxy requests in and out of a cluster of somewhat more fully fledged Web servers like Apache or Litespeed. It has some great features like its compiled language, called VCL, and C-like programming API. Large vBulletin deployments tend to be heavy on CPU and [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fblog.unixy.net%2F2009%2F11%2Frunning-vbulletin-along-with-varnish%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fblog.unixy.net%2F2009%2F11%2Frunning-vbulletin-along-with-varnish%2F&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>Varnish is an excellent Web accelerator that can be made to proxy requests in and out of a cluster of somewhat more fully fledged Web servers like Apache or Litespeed. It has some great features like its compiled language, called VCL, and C-like programming API.</p>
<p>Large vBulletin deployments tend to be heavy on CPU and memory due to PHP script processing. For a large vBulletin forum, we recommend a cluster of 5 physical servers with three of those running Xen virtualization. One of those servers will be dedicated to the MySQL master database. Three to be setup as &#8220;headless&#8221; PHP nodes and Varnish load balancing and failover. And finally one as the NFS file store. The three headless servers need to run Varnish in their own VM and Litespeed or Apache in their own VM similarly.</p>
<p>The varnish backend director functionality makes it ideal to balance incoming traffic across all PHP headless nodes. It makes the configuration scalable and plug and play especially when needing to scale out within hours. The challenge in this setup is in making Varnish work correctly with vBulletin. Otherwise, session problems will occur.</p>
<p>We have a lot to share on this implementation so keep checking this blog as we will post it all. In the next installment, we&#8217;ll go through our deployment of a large vBulletin forum for a customer. In the mean time, feel free to get in touch should you have a question or comment. If you are interested in us helping you accelerate your server, we have a page explaining the different technologies we deploy on our clients&#8217; dedicated servers. Read up here: <a href="http://www.unixy.net/accelerate-your-server/"><strong>http://www.unixy.net/accelerate-your-server</strong></a></p>
<p><strong>Update</strong>: we are offering a Varnish configuration for vBulletin (3 &#038; 4) for a one-time fee. We can also configure it free of charge should you decide to rent your fully managed dedicated server from UNIXY (http://www.unixy.net). Please <a href="http://www.unixy.net/contact-unixy">contact us</a> today to get your forum running with a blazing fast speed!</p>
<p>That&#8217;s all folks!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.unixy.net/2009/11/running-vbulletin-along-with-varnish/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
