We use Pingdom a lot here; we have 65 checks running at the moment, we publish our uptime reports for the most important ones, and we have our own-made Pingdom status screen up in the main office but we all miss the old Desktop Notifier. This died when Pingdom deprecated their v1 API and it seemed that neither they, nor the community, were going to provide a replacement any time soon, so here is ours; "Desktop Notifier for Pingdom".
Recently by Richard Benson
The EU Directive on Privacy and Electronic Communications initially caused quite a stir 12 months ago, but the UK's Information Commissioner's Officestepped in and said that UK firms would have a year to comply with the regulations. That year is up on 26th May and people are starting to talk about the EU Cookie Law again, however no-one seems to be exactly sure what the implications will be and the ICO is not offering answers to the questions people are asking.
What is the directive about?

Often when using the command prompt in Windows Vista and Windows 7 you'll need to run the command as an Administrator and whilst running a command prompt elevated is not tough, it's fiddly. If you've forgotten to do it before you've moved your way around the file system it can be very annoying.
sudo <your-command> <arguments>
The code is available on our GitHub. There is a pre-compiled binary available, but check your dependencies first.
In this article we are going to cover MySQL Cluster, it's installation on Debian (Lenny), Master-Master replication and how to tie all this together with HAProxy for a very high availability solution.
There are a number of solutions to this with MySQL and every situation will require a different response, there are a lot of good articles out there to help you decide which solution is best. In this article we will be covering MySQL Master-Master replication and installation on Debian (Lenny) using Rackspace Cloud Servers.
The standard model of MySQL replication is a single master with multiple slaves, which provides you with very good read reliability, but writes can only be made to the master node. This means that if the master fails, you can't just switch to another node and carry on as before, your slaves will become out of sync. Additionally you can't load balance between your nodes for reads and writes. By using a multiple master configuration, you can drop a node at any point and either switch your connection string to using the remaining master, or use load balancing and failover with HAProxy.
In this article we will cover basic saving and loading of IPTables rules in Debian/Ubuntu on shutdown and boot up as well as common rules that go with our other guides.


