File: INSTALL

package info (click to toggle)
msql 2.0.3-5
  • links: PTS
  • area: non-free
  • in suites: hamm, slink
  • size: 3,596 kB
  • ctags: 2,483
  • sloc: ansic: 34,769; sh: 1,309; yacc: 1,084; perl: 328; makefile: 267
file content (81 lines) | stat: -rwxr-xr-x 3,882 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
Installation instructions for mSQL Version 2.0
---------------------------------------------- 

NOTE :	A complete guide to the compilation, installation and
	configuration is included in the first section of the User
	Guide.  Installation troubleshooting information is also
	included in the User Guide for those having problems installing
	mSQL.  The User Guide can be found in the doc/ directory of this
	distribution.

------------------------------------------------------------------------------
A quick outline of the installation process is given below.


1.	Unpack the source code.

2. 	In the root directory of the distribution type "make target".  This 
	will create a "symbolic link tree" for your platform under the 
	targets/ directory.  For example, on a BSD/OS machine you may end up 
	with a replica of the source code directory in targets/BSD_OS-2.1-i386/

3.	Change directory to the target directory for your machine.

4.	Run the setup utility (Note: use ./setup to ensure you get the
	mSQL setup utility and not a system utility).

5.	After setup has completed,  you can edit a couple of default
	configuration values in site.mm if you wish.  When you are happy
	type "make all"

6.	If the compilation of mSQL completes properly, type "make install"
	This will install all the mSQL related files under /usr/local/Hughes
	(or whatever directory you set as the install directory in site.mm) 
	You may need root access to perform this step.

7.	Edit /usr/local/Hughes/msql.conf to see if everything is OK.
	The only thing you might change in a normal installation is the
	username of the mSQL_User or the Admin_User.  By default, mSQL is 
	configured to run as a user called 'msql' with root being the admin
	user (i.e. the one who can create databases, shutdown the server
	etc).

8.	Ensure that the installation directory (and everything under it)
	is owned by the user that mSQL will run as (e.g. the msql user).
	To do this, issue a command like "chown -R msql /usr/local/Hughes".
	Substitute the correct username and installation directory if
	you are running a non-default installation.

9.	If you wish to use the WWW interface package, W3-mSQL, you
	should start the mSQL server (by running /usr/local/Hughes/bin/msql2d &)
	and then execute misc/setup_w3auth.  This will setup a couple of
	databases and install the Hughes Technologies related web page
	graphics etc. into your web tree.  You'll need to be running as
	the mSQL Root_User as this creates several databases.  You may
	also need to run as a specific user to modify your web tree.
	Note : setup_w3auth expects to find Lite installed in the default
	location.  If you installed into anywhere other than
	/usr/local/Hughes please edit the first line of the
	setup_www script to reflect the location of the Lite binary.

10.	If you want to use W3-mSQL you'll need to copy w3-auth and
	w3-msql from /usr/local/Hughes/bin to your cgi-bin directory (or
	provide a symbolic link to them from your cgi-bin).  You will
	also need to copy the graphics files used by these tools into
	your web tree.  Create a directory called 'Hughes' at the top
	of your web tree and then copy the demos/w3-msql/graphics
	directory into the newly created 'Hughes' directory (i.e.
	using a browser you could load
	http://your.host/Hughes/graphics/hughes.gif)

11.	If you want to install the sample W3-mSQL application (the 
	bookmarks database), read the README file contained in the
	demos/w3-msql/bookmarks directory.


Note : To use the W3-mSQL authentication / access control features
you'll need a web server that passes authentication headers to CGI
scripts.  The CERN server does this and a patch is available from Hughes
Technologies to add this feature to the Apache server.  The Apache patch
is available for both 1.1 and 1.2 versions of Apache.  Please see the
Software section of www.Hughes.com.au for details.