Running multiple servers is documented in the manual <http://dev.mysql.com/doc/mysql/en/Multiple_servers.html>. Using clients in a multi-server setting is documented on one of the sub-pages.
4.0.13 is over a year old (May 16, 2003). Current version is 4.0.20. A lot has been done in the interim <http://dev.mysql.com/doc/mysql/en/News.html>. Unless you have a specific reason not to, I'd recommend upgrading to 4.0.20.
Michael
sean c peters wrote:
Hi all, I am looking to upgrade to MySQL 4.0.13 on a Solaris production server, and would like to install and test 4.0.13 without disturbing the existing 4.0.2 server, so that there will be minimal downtime when actually upgrading the production system. So, i should be able to compile 4.0.13 without any problems, by just havnig a different base directory. But, by default, MySQL reads /etc/my.cnf at startup, so im wondering if i'll need to switch out the /etc/my.cnf files depending on which server I'm starting. Also, since client programs get options from that same file, it appears that there will be a problem running them both concurrently, because when a client connects, it will need to read the proper my.cnf, and if i have different clients connecting to each server i'd need to keep switching the files, but i cant realistically know in advance when clients are connecting to which server, so this will not work properly. Can i compile mysql with a different configuration so that it reads the default my.cnf from somewhere else, say /sandbox/etc/my.cnf for instance?
Any other problems with running concurrent MySQL servers on the same machine?
thanks much sean peters [EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
