Connect to your Virtual Server via Telnet or SSH and run the mSQL v2.0.x installation script that matches your virtual server operating system:

FreeBSD % vinstall msql

BSDI BSD/OS % installmsql2

NOTE: To find out which operating system your virtual server is running, use the uname command.

The mSQL v2.0.x installation scripts will perform the following tasks:

• Copy the mSQL v2.0.x files onto your Virtual Server.
• Determine if you have msql v1.0.x installed. If you do have msql v1.0.x installed, the mSQL v2.0.x installation scripts will attempt to convert your existing database files to v2.0.x database format. The scripts will not destroy your v1.0.x database directory: ~/msqldb.
• Create an msql.acl file with some "intelligent" defaults.

mSQL v2.0.x uses different command-line commands than v1.0.x of mSQL. The following table summarizes the differences:

Some "aliases" will also be created in your ~/.cshrc file to help you remember. You will need to do the following at the command prompt before these aliases take affect:

% source ~/.cshrc

You only need to do this the first time. When you log in again the changes will be in effect.

Your v2.0.x databases are stored in the following directory, depending on your virtual server operating system:

FreeBSD ~/usr/local/Hughes/msqldb

BSDI BSD/OS ~/usr/local/msql2/msqldb

If you are upgrading from v1.0.x, you will eventually want to remove the mSQL v1.0.x directory ~/msqldb manually when you are certain the upgrade worked. You can do this by typing the following at a command prompt:

% rm -rf ~/msqldb

Make sure your databases are working correctly before doing this.

Starting mSQL

To start the mSQL daemon use the following command:

% daemon -f /usr/local/bin/msql2d

Notice that a similar command has been added to your ~/etc/rc file to ensure that mSQL restarts in case of a host machine reboot. mSQL runs as a daemon on your Virtual Server. To check on the status of the mSQL daemon, do the following:

% ps auxww | grep msql