Efficiency vs. Inefficiency, in a no-holds barred fight.
admin OK, so maybe its not a complete secret, but after around 10 years of running WordPress I only just found out about it. Here it is. After you've logged in as admin, go to the following URL. i.e. type options.php into the URL of your site: Obviously you have to be logged in as admin. … Read more
So you forgot to pay your bill. It happens. PLDT used to set an automated phone call to call you once a day until you paid. Now they have something much more irritating, and something that feels borderline illegal. What they do is they hijack your internet connection. Every four or five page loads, they … Read more
Useful one to have appear in your inbox in the morning. Have just done this on a server, so I thought I'd put it here to remind myself. This works for debian and Ubuntu variants, which have the apt command (a meta-script for the apt-get ecosystem) In note form … Add the following text to … Read more
There are a lot of posts around telling you how to update mysql root password. "Simple!," they cry, "just start mysqld_safe, and use mysqladmin …" But wait, what's that? You don't HAVE mysqld_safe? Well the chances are, you've got one of these new fangled systemd systems, where everything is ass backwards.
Then you went and tried to run mysqld as root didn't you? That didn't work either. Read on …
I have a small VPS server which hosts a couple of low traffic websites. I've been battling it for a couple of years, trying to reduce the memory consumption. The VPS has 0.5Gb RAM, and the same sized swap file. Sure, I could upgrade the VPS, but sometimes this geeky battling stuff is half the fun!
I've been using the two obvious Mysql tuning scripts and altering the configuration gradually over the last year or so. If you've ever looked at any of this yourselves you'll know them: mysqltuner.pl and tuning-primer.sh
So the problem was this. I'd start up Mysql and it would eat up all the memory, start swapping, and eventually invoke oom_killer. The first change I made was to disable innodb. I didn't need it on this server, and immediately memory usage of MySQL dropped to about half. Now it would start up fine, and run for a week or two, but eventually it would crash out. It was using about 300Mb of the available 512Mb RAM, but would eventually use up all the swap as well. I set up monit to watch it and restart it when that happened, but that wasn't a great solution, so I started chipping away at the my.cnf file, to reduce memory footprint.