my.cnf Problem

[BradE]

We are running a vBulletin based forum and are having problems with using my.cnf to optimize. Our default setup was /.my.cnf and only listed our client name and database. One of the members of the vB devlopment team was nice enough to give us some suggestions to optimize, I applied the changes to the file and restarted SQL. That is where the problem begins. vB has a feature built into its diagnostics that allows you to check the SQL variables, and after the SQL restart the changes in the .my.cnf were not reflected. We though it could be a location problem, so I removed the client and password info, renamed to my.cnf to act as a global file, and I moved it to /etc/my.cnf and restarted SQL, it still doesn't update. :confused:

What are we doing wrong?

[Robert]

Hi there,

/etc/my.cnf should be a correct location. Open a ticket with support if you're still having issues. Be sure to give them URLs, paths, etc. Anything they might need to be able to replicate the issue.