The WordPress.com stats helper monkeys prepared a 2013 annual report for this blog.
Here’s an excerpt:
The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 17,000 times in 2013. If it were a concert at Sydney Opera House, it would take about 6 sold-out performances for that many people to see it.
Click here to see the complete report.
Recently I had to work with a large amount of data that had to be imported into MySQL via a script after being modified. I’ve found that using LOAD DATA was the quickest way to do the job.
If you are using Ubuntu for your server (or you have to work with a server using Ubuntu) you will find this error when trying to use the query:
ERROR 29 (HY000): File '....' not found (Errcode: 13)
After few seconds on Google you will find many users that managed to get over the error using the keyword LOCAL, but if you keep your MySQL updated you will see that it will not work as it could generate a security issue in your server.
To overcome this issue there is a simple workaround that require you to modify the MySQL’s AppArmor file and define directory where the program can read and write.
Be aware that allowing MySQL to read and write in a directory could lead to security problems, always review this kind of changes with a System Administrator.
The workaround is really quick:
- Open the file /etc/apparmor.d/usr.sbin.mysqld as root with your favourite text editor
- You should see a list of paths where AppArmor allow MySQL to write and read, at the end of this list add the directory where you would like that MySQL will be able to read and write following the pattern used in all the previous entries. For instance:
#This will be your dir definition
Then save and close the file.
- After you have successfully modified the file it is time to tell AppArmor that it needs to reload the configurations, so as root execute the following command:
# /etc/init.d/apparmor reload
- Then restart MySQL, as root execute the following command:
# service mysql restart
At this point you have allowed MySQL to write and read contents into your defined directory, only do this if you know what you are doing! I take no responsibility for any damage or data loss caused by a server not correctly secured.
Be careful & have fun!