Automysqlbackup is a great tool. It's setup and configuration can be found at many other sites. When you try to run it out of the box, you will get something like this:

./automysqlbackup.sh.2.5: Command not found.

To run it in FreeBSD, you need to edit a single …

I know I did this the hard way. there is a command that you can issue that will convert them on the fly. what I did was mysqldump the database, reinstall mysql(because of other reasons), and then edit the dump so that the line that specified the engine reads …

Screwed around for a bit. messed up MySQL. I decided to remove --purge, and start fresh. Unfortunately, the reinstall wouldn't work. Long story short, i had to remove "mysql-server, mysql-server-5.0, and mysql-common". when i ran this, it also pulled out other dependencies, but i just reinstalled them all. voila …

I completely. completely messed up MySQL. Badly. I wiped out the data directory (/var/lib/mysql in Debian) and the went to remove mysql ... apt-get remove --purge mysql-server That only deleted something like 86K. dissapointing. It looks like "mysql-server" is a shortcut pointing to the latest version of the software …

FreeBSD does not automatically include a default my.cnf for MySQL. Instead, a set of sample configuration files can be found under /usr/local/share/mysql. These configuration files include my-small.cnf, my-medium.cnf, my-large.cnf, my-innodb-heavy-4G, and my-huge.cnf. The appropriate file can be copied and used as a …

note to self... do NOT kill mysql processes from phpmyadmin's control panel and force mysql to quit. Bad things happen. In this case, mysql wouldnt start again. InnoDB's indexes, binary logs, etc. were all out of sync. The 20 page log explaining all the ways the DB couldn't start is …