Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Lloyd Zusman (ljzasfast.com)
Date: Sat Sep 15 2007 - 20:52:08 CDT
I'm running mysql-5.0.46 on a linux system on a VPS. As such, the yum package
manager is being used to install a standardized mysql installation, and I due to
other system dependencies, I can't change this.
I need a second mysql installation on that machine that runs under a completely
different directory tree and is totally separate in all ways from the standard
installation. Therefore, I downloaded the source and compiled it to install
itself under the /usr/private directory tree. I did this as follows:
I did a "make" followed by a "make install", and everything indeed got
installed under the /usr/private tree. However, the various programs
still seem to be looking by default in /etc for the "my.cnf" file. Since
/etc/my.cnf is the file that the standard version of mysql uses, this new,
private version tries to point to the directories that are specified in the
old version's configuration, which is clearly not what I want it to do.
I was hoping to get it to look for a second "my.cnf" file inside of
/usr/private/etc, but that isn't happening.
It seems like the build is ignoring the --sysconfdir parameter, at least
with regard to the location of the "my.cnf" file.
What am I doing wrong? Or is this some sort of deliberate feature of mysql?
Thanks in advance for any light you can shed on this.
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql