If you know how impossible it is to find this link when you need it.
Valid for Windows XP & Windows 2003 Server

%windir%explorer.exe "hcp://CN=Microsoft%20Corporation,L=Redmond,S=Washington,C=US/Remote%20Assistance/Escalation/Unsolicited/Unsolicitedrcui.htm"

Server 2008

%systemroot%system32msra.exe

I recently moved my website to a cheap VPS I had the fun journey of trying to get it work without grinding to a halt everytime I clicked on a page, which you ‘should’ have noticed is fixed.

Firstly I needed to be realistic this blog wouldn’t have more than two simultanious connections at once, with that known I could then edit the amount for apache server threads to an un-godly small number in /etc/apache2/apache2.conf

StartServers 2
MinSpareServers 2
MaxSpareServers 2
MaxClients 20
MaxRequestsPerChild 0

With that noted a quick look at ‘top’ shows MySQL eating lots of Virtual Memory a quick swap of the configuration file: /usr/share/doc/mysql-server-5.1/examples/my-small.cnf to /etc/mysql/my.cnf sorts out that problem. (Don’t forget to backup your originals)

And finally modifying the WordPress max memory limit as noted in this post
suhosin[10882]: ALERT – script tried to increase memory_limit to 268435456 bytes

Again after the fun times of being to cheap too pay for a good provider and hosting this website from a low end VPS with limited memory running WordPress and MySql, I have finally tuned it so that it no longer uses swap! yay!

Anyway I had trouble getting permalinks working and knowing nothing about them I set off in my investigation. It appears that permalinks require mod_rewrite to be enabled. After checking in mods_avaliable and search debian repos, I came up blank. It seems that you need to enable mod_rewrite via the command

 a2enmod rewrite 

Too Easy!

After moving from web hosting to a low spec VPS Provider (read: less ram) I noticed the following errors in my apache2/access.log:

vps suhosin[10882]: ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘MY.IP.ADD.RESS’, file ‘/var/www/blog/wp-admin/admin.php’, line 109)

When trying to access parts of the WordPress dashboard. The required fix was that WordPress wanted 256MB of memory (which I didn’t have).

The fix involved editing: wp-includes/default-constants.php
line 28: define( ‘WP_MAX_MEMORY_LIMIT’, ’256M’ );
to something a little more reasonable like 64M

Just a quick post with a link of some great security videos: http://www.securitytube.net and a interesting blog: http://r00tsec.blogspot.com.au