Start - The complicated way of getting boinc to play with the new way MySQL is setup
On the server the boinc server we created look at your mysql conf file, mine is /etc/mysql/my.cnf, it will be something like that. Inside that file you need to figure out where the socket is running, mine is /var/run/mysqld/mysqld.sock
BOINC expects that will be running in either /var/lib/mysql/mysql.sock or /tmp/mysql.sock. Change that in /etc/mysql/my.cnf and /etc/mysql/debain.cnf and restart the mysql server. It is a good idea to backup these files first!
Once the location has been changed in the cnf files, you can stop the service "service mysql stop" and start it again "service mysql start"
End - The complicated way of getting boinc to play with the new way MySQL is setup
The easy way is to just make it accessible from the tcp socket, rather than move or link the location it runs in
Ran into some access problems with the user I created, you can restart mysql directly and get around the security to reset your password by
On the server, in the boinc server folder we already built
./tools/make_project --url_base http://192.168.1.199 --db_user root --db_passwd mysqlrootpw mythGrid
Where mythGrid is the project name, local network address of server vm --url_base http://192.168.1.199, --db_host 192.168.1.199 being the address of the database host we set for our VM's mysql server earlier, --db_user root being the username we set for our VM's mysql server earlier, and --db_passwd mysqlrootpw the password we set for our VM's mysql server earlier
If you make any mistakes you can over write the previous installs with the flags --delete_prev_inst --drop_db_first