Hi:

I've been running 3.23 for years, but several users are clamoring for new versions, as many php apps are using newer features, so I downloaded the source for 5.0.51b to run on a different TCP port.

I found a reference on a couple of ways to do this here:

http://dev.mysql.com/doc/refman/5.0/en/multiple-unix-servers.html

It looked pretty straightforward to me. Since I prefer to do as much non-standard stuff at runtime as possible, rather than compile it in, the only configure option I changed was --with-prefix=/usr/local/mysql50 (3.23 is installed in /usr/local from FreeBSD Ports).

The rest, from what I could gather from the page above could be done thusly:

#!/bin/bash
/usr/local/mysql50/bin/mysqld_safe --socket=/tmp/mysql50.sock \
--port=(new port) --basedir=/usr/local/mysql50 --datadir=/var/db/mysql50 &

I did the datadir as well, because I had read that sometimes accessing existing 3.23 databases using 5.0 can cause problems, so I thought I'd start fresh. I don't run a my.cnf as yet.

However, the server still seems hopelessly confused. If I telnet to port 3306, I get the old version as I should and when I telnet to the new port I get the new version as I should, but if I do a:

mysqladmin -P (new port) variables

I get the old variables. Similarly, if I install phpMyAdmin and specify the new port and socket, it still sees the old databases and version of MySQL. Start and stop scripts also seem confused. What did I miss?

James Smallacombe                     PlantageNet, Inc. CEO and Janitor
[EMAIL PROTECTED]                                                           
http://3.am
=========================================================================

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to