Hot piss. Has it really been that long? Yes, it has. Governments have risen and fallen; seasons have changed outside the window; popular kids refer to my previous post when in need of a clichéd example of something unfashionable from history.
The last 12 months in summary: I graduated 2.1 with honours from Warwick and immediately started a promising job as IT Manager for my old employer which degenerated at terrifying speed into a micro-managed clusterfuck from which I extracted myself six weeks ago, turning to my long-time side-passion of web design.
![]()
Xbox 360 UK Repair Timeline: A Gamer’s Renaissance Tale of Woe
When I was still at school I had a big thing for PC and video games. I used to run a Counterstrike clan, played a lot of random FPS/RTS/wtf titles and had a great time doing so. On the console side I’ve always been a bit behind the times — had a SNES quite some time after they came out, an N64 (with GoldenEye, of course) the Christmas after they were released, and more recently a GameCube and some borrowed time on my brother’s PS2. I didn’t even get a Game Boy until the Color version came out. But I was usually reasonably up to speed with PC gaming, from the days of Doom onwards.
![]()
Sanity, Solitude And The Death Rattle of Productivity
These are strange times. Someone once tried to apply Einstein’s Theory of Relativity to produce something to the effect of “work to be done expands to fill the time available to do it.” Conversely, I’m experiencing something of the opposite, a sad failure of self-discipline where amount of free time and apathy toward work and study are set up in a tragic correlation.
![]()
Fix Debian Exim4 Broken By Upgrade
Thought I’d just post this since I didn’t find an authoritative answer on the web. Those using exim4 on a Debian testing or unstable system might recently have found their system broken after doing a dist-upgrade to version 4.67−7, with exim4-config failing to configure with a message similar to the following:
Exim configuration error in line 28 of /var/lib/exim4/config.autogenerated.tmp: malformed macro definition.
Solving Slow Apache/PHP; Culprit = ClamAV
I’ve been having a lot of problems recently with my home Debian server locking up, with Apache processes swelling up until all RAM is eaten up and CPU 100% utilised. The box stops responding until I can get local access and restart Apache. This used to happen several times a week, despite actual load on the server being very low with hardly any web requests.
I put this down to the age of the install and some dodgy Apache settings and didn’t look too much into fixing it; I turned the child process settings down a lot which didn’t improve things, so I just set a cron job up to restart apache every so often. It was only when I came to install Debian on a brand-new server at work that I realised something was afoot — the Apache/PHP install on this new server was doing the same thing — locking up several times a day for no apparent reason and in the exact same way. Both servers would suddenly experience massive CPU and RAM utilisation; additionally Apache would take several minutes to get from startup to actually accepting requests, with huge CPU use in that time. Incidentally, my home box is testing/unstable and this new server is Etch (stable).
I spent a few minutes going through the config files for Apache, PHP and MySQL (also installed on my home box) in an effort to optimise the install, and examined the extensions list in php.ini to see if there were any I could remove. I unfortunately suffer from over-enthusiasm when installing things like PHP, XMMS and so on, whereby I read the list of related packages and install everything that I might possibly need someday or that could be useful at some point. In this case this included php4-clamavlib, which I installed thinking it might be good to play with on a rainy day.
A quick apt-get remove php4-clamavlib and I restarted Apache; to my surprise it came up in about two seconds as opposed to the three minutes it was taking before to stop using 100% CPU after being started. I watched the box carefully for the rest of the day and it had no problems. Upon getting home I did the same thing on my own server and it too appears to be cured. So if you’re having problems with Apache suddenly choking, check to see if you’ve got the ClamAV library for PHP installed. If you don’t need it, lose it!
![]()
Also: Portable Fear and Loathing