MySQL is pretty good about following symlinks. Move /var/lib/mysql to /mnt/ramdisk/mysql and then symlink to it.
# ln -s /mnt/ramdisk/mysql /var/lib/mysql Changing where everything resides in my.cnf should have been sufficient but the symlink way works great as well. And there should be no performance hit. I'm fairly certain I've read in the docs that it traverses a symlink to it's source directory and proceeds to access the files there instead of hitting the symlink every time. Also, take PHP out of the loop at first. Try accessing it via the command-line mysql client first and after you get that working, then introduce extra variables like apache/php into the mix. PS. Check permissions as well.. /mnt/ramdisk/mysql needs to very closely match the permissions of /var/lib/mysql (as well as owner/group). -----Original Message----- From: Creigh Shank [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 19, 2003 8:35 AM To: MySQL Users Subject: Moving MySQL data to RAMDisk On moving my data files from /var/lib to /mnt/ramdisk I seem to be missing something. I've changed every .ini and .conf file I can find (/etc/my.cnf, /etc/init.d/mysql, /etc/init.d/mysqld, /etc/php.ini and /etc/httpd/conf/httpd.conf (for DAV-lock)). MySQL seems to start ok, but when I use my application through Apache the error message is that MySQL is not running (I think it's just not finding it). Any suggestions? Creigh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
