Upgrading MSQL
According to my calculations, the version of MSQL we are currently running, will expire on May 2, 1997. The version we have running is 2.0 Beta 4. Three days ago Beta 5 was release, but it seems to be quite buggy, I can barely get it to compile. So I have not upgraded to Beta 5, which only expires a week later than Beta 4 anyway. But, eventually, you will need to upgrade to a newer version of msql. Here are some guiding steps to take to accomplish this:
It is a good idea to dump your database(s) to files before wasting the datbase. To do this, run the command:
% msqldump dbname > dbname.msql
where dbname is the name of the database to dump.
You should also kill any applications that may have connections to the msql database server, namely the KB server. Eventually, there should be a nicer way to shutdown the KB server, but for now, this is how you have to do it:
% ps -u bradley | grep siserver | sort
where you substitute in the user that the KB server is run as for bradley. (On NeXT, the command looks like: 'ps -aux | grep siserver | sort'. Then find the PID of the top line returned from this command and use it in the command:
% kill PID
this should shutdown all KB server processes.
Next, you need to shutdown the msql database server. To do this, execute the command:
% msqladmin shutdown
and wait until you see the "shut down complete" message.
Now you need to remove the MSQL directory. Currently this is /usr/people/bradley/MSQL. Do this with the command:
% rm -rf /usr/people/bradley/MSQL
To get the source code for the new version of the msql server, go to the msql home page at:
and download the current version of msql. This file you download wil most likely be named msql-xxx.tar.gz. To uncompress and untar this file, enter the commands:
% gunzip msql-xxx.tar.gz % tar -xvf msql-xxx.tar
This creats a directory named something like: msql-xxx. Inside this directory will most likely be a file named INSTALL with installation instructions. You will need to modify some configuration files that specify which user the server is run as and what the path is to the install directory. The installation instructions will tell you how to do this. NOTE: Beta 4 installed on the SGIs for me with absolute ease. Beta 5, however, had many bugs in it, and I had to actually hack some of the C code just to get it to compile (who knows if it would have even worked correctly...). So we'll have to see how easy future versions are to install... After compilation and installation, you may want to edit the file msql.conf in the installation directory, to specify the user and path the server should run with.
If you did not properly wait until the previous version server shutdown completely before removing hte directory, you may have to reboot the computer before the new server wil run. This is becuase if you do not wait for the old server to properly shutdown, it does not have chance to clean up it's UNIX domain socket, and the new version will think that socket is already in use and will not start.