<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.0.7" -->
<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/"
	>

<channel>
	<title>Design Solution Blog - Web Development &#038; Hosting : Technically Speaking</title>
	<link>http://blog.designsolution.co.uk</link>
	<description>Web Development &#038; Hosting : Technically Speaking</description>
	<pubDate>Wed, 13 Jun 2007 15:51:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>
	<language>en</language>
			<item>
		<title>MySQL binary log rotation</title>
		<link>http://blog.designsolution.co.uk/mysql-binary-log-rotation/</link>
		<comments>http://blog.designsolution.co.uk/mysql-binary-log-rotation/#comments</comments>
		<pubDate>Thu, 18 Jan 2007 12:56:13 +0000</pubDate>
		<dc:creator>glen</dc:creator>
		
		<category>General</category>

		<category>MySQL</category>

		<category>RedHat</category>

		<guid isPermaLink="false">http://blog.designsolution.co.uk/mysql-binary-log-rotation/</guid>
		<description><![CDATA[We are running a MySQL replication setup, and find that the binary logs get very large, very quickly.  Since MySQL didn&#8217;t come with a log rotation script, we rolled our own.  Usage is simple:
At the top of the script are some definitions that you need to change for your setup:

MYSQL_USER MYSQL_PASS - You [...]]]></description>
		<wfw:commentRss>http://blog.designsolution.co.uk/mysql-binary-log-rotation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Preventing Apache DOS attacks</title>
		<link>http://blog.designsolution.co.uk/preventing-apache-dos-attacks/</link>
		<comments>http://blog.designsolution.co.uk/preventing-apache-dos-attacks/#comments</comments>
		<pubDate>Tue, 02 Jan 2007 12:32:49 +0000</pubDate>
		<dc:creator>glen</dc:creator>
		
		<category>General</category>

		<category>Apache</category>

		<category>RedHat</category>

		<guid isPermaLink="false">http://blog.designsolution.co.uk/preventing-apache-dos-attacks/</guid>
		<description><![CDATA[We&#8217;ve recently come under attack from denial-of-service (DOS) attacks.  In order to alleviate this situation, we are currently testing out the mod_evasive Apache module.
mod_evasive v1.10.1
The install was simple.  After downloading and unpacking the source code&#8230;
/usr/sbin/apxs -i -a -c mod_evasive20.c
This will compile the module, copy it to the correct directory and enable the module [...]]]></description>
		<wfw:commentRss>http://blog.designsolution.co.uk/preventing-apache-dos-attacks/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Optimizing MailScanner</title>
		<link>http://blog.designsolution.co.uk/optimizing-mailscanner/</link>
		<comments>http://blog.designsolution.co.uk/optimizing-mailscanner/#comments</comments>
		<pubDate>Mon, 18 Dec 2006 13:05:59 +0000</pubDate>
		<dc:creator>glen</dc:creator>
		
		<category>General</category>

		<category>RedHat</category>

		<category>Email</category>

		<category>MailScanner</category>

		<guid isPermaLink="false">http://blog.designsolution.co.uk/optimizing-mailscanner/</guid>
		<description><![CDATA[Our MailScanner installation is pretty heavily utilised, scanning 20,000+ messages a day.  I&#8217;m always looking for ways of improving it&#8217;s performance, so the following document has proved useful:
Optimization tips

Use a ramdisk (tmpfs) for MailScanner’s working directory.
Make sure you have enough ram
Set the noatime flag on your spool and log partitions
Use a local DNS caching [...]]]></description>
		<wfw:commentRss>http://blog.designsolution.co.uk/optimizing-mailscanner/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
