|
version 1.6, 2001/02/12 17:38:13
|
version 1.8, 2001/02/14 14:33:35
|
|
Line 20 and a SQL database.
|
Line 20 and a SQL database.
|
| <LI>Current status of documentation</LI> |
<LI>Current status of documentation</LI> |
| <LI>Current status of implementation</LI> |
<LI>Current status of implementation</LI> |
| <LI>Purpose within LON-CAPA</LI> |
<LI>Purpose within LON-CAPA</LI> |
| |
<LI>Dependencies</LI> |
| <LI>Installation</LI> |
<LI>Installation</LI> |
| <LI>Installation from source</LI> |
<LI>Installation from source</LI> |
| <LI>Configuration (automated)</LI> |
<LI>Configuration (automated)</LI> |
|
Line 55 Right now, a lot of "feasibility" work h
|
Line 56 Right now, a lot of "feasibility" work h
|
| Recipes for manual installation and configuration have |
Recipes for manual installation and configuration have |
| been gathered. Network connectivity of lond->lonsql->lond->lonc |
been gathered. Network connectivity of lond->lonsql->lond->lonc |
| type tests have been performed. A binary installation |
type tests have been performed. A binary installation |
| has been compiled in an RPM (LON-CAPA-mysql). |
has been compiled in an RPM (LON-CAPA-mysql, with perl components |
| |
a part of LON-CAPA-systemperl). |
| The most lacking test in terms of feasibility has |
The most lacking test in terms of feasibility has |
| been looking at benchmarks to analyze the load at which |
been looking at benchmarks to analyze the load at which |
| the SQL database can efficiently allow many users to |
the SQL database can efficiently allow many users to |
|
Line 141 THE SOLUTION:
|
Line 143 THE SOLUTION:
|
| processes (lonsql's) handle the MySQL database manipulations. |
processes (lonsql's) handle the MySQL database manipulations. |
| </PRE> |
</PRE> |
| </P> |
</P> |
| |
<H2>Dependencies</H2> |
| |
<P> |
| |
I believe (but am not 100% confident) that the following |
| |
RPMs are necessary (in addition to the current ones |
| |
in rpm_list.txt) to run MySQL. Basically I discovered these |
| |
dependencies while trying to do external RPM based installs. |
| |
I assume, and sometimes found, that these dependencies apply |
| |
to tarball-based distributions too. (So to play it on the |
| |
safe side, I am going to include these RPMs as part of the |
| |
core, minimal RPM set.) |
| |
<UL> |
| |
<LI>egcs-1.1.2-30</LI> |
| |
<LI>cpp-1.1.2-30</LI> |
| |
<LI>glibc-devel-2.1.3-15</LI> |
| |
<LI>glibc-devel-2.1.3-15</LI> |
| |
<LI>zlib-devel-1.1.3-6</LI> |
| |
</UL> |
| |
|
| |
</P> |
| <H2>Installation</H2> |
<H2>Installation</H2> |
| <P> |
<P> |
| Installation of the LON-CAPA SQL database normally occurs |
Installation of the LON-CAPA SQL database normally occurs |
| by default when using the LON-CAPA installation CD |
by default when using the LON-CAPA installation CD |
| (see http://install.lon-capa.org). It is installed |
(see http://install.lon-capa.org). It is installed |
| as the LON-CAPA-mysql RPM. This RPM encodes for the MySQL |
as the LON-CAPA-mysql RPM. This RPM encodes for the MySQL |
| engine and related perl interfaces (Perl::DBI, Perl::Msql-Mysql). |
engine. Related perl interfaces (Perl::DBI, Perl::Msql-Mysql) |
| |
are encoded in the LON-CAPA-systemperl RPM. |
| </P> |
</P> |
| <P> |
<P> |
| The three components of a MySQL installation for the |
The three components of a MySQL installation for the |
|
Line 172 actual MySQL functionality on the system
|
Line 194 actual MySQL functionality on the system
|
| </P> |
</P> |
| <H2>Installation from source</H2> |
<H2>Installation from source</H2> |
| <P> |
<P> |
| |
Note: the mysql site recommends that Linux users install by |
| |
using the MySQL RPMs (MySQL-client, MySQL, MySQL-shared, etc). |
| |
While these RPMs work, I was unsuccessful at integrating |
| |
this RPM-installed database with perl modules from www.cpan.org. |
| |
Hence, I <STRONG>strongly</STRONG> recommend that, when installing |
| |
from "source", MySQL and the perl components be in fact installed |
| |
from their tarballs (.tar.gz, .tgz). (Perl components, when installed |
| |
from RPMs, also wound up in incorrect locations on the disk.) |
| |
Do not coordinate a source install with externally made RPMs! |
| |
It is, of course, okay to use LON-CAPA RPMs such as LON-CAPA-systemperl |
| |
and LON-CAPA-mysql since we, in fact, made these RPMs correctly :). |
| |
<UL> |
| |
<LI>http://www.cpan.org/authors/id/JWIED/Msql-Mysql-modules-1.2215.tar.gz |
| |
<BR>This tarball Released 20th August 2000 |
| |
<LI>http://www.mysql.com/Downloads/MySQL-3.23/mysql-3.23.33-pc-linux-gnu-i686.tar.gz |
| |
<BR>This tarball Last changed 2000-11-11 |
| |
<BR>This is actually a binary tarball (as opposed to source code |
| |
that is subsequently compiled). |
| |
<LI> |
| |
<BR> |
| |
</UL> |
| |
</P> |
| |
<FONT COLOR="green"> old notes in green |
| |
<P> |
| The following set of tarballs was found to work together |
The following set of tarballs was found to work together |
| properly on a LON-CAPA RedHat 6.2 system: |
properly on a LON-CAPA RedHat 6.2 system: |
| <UL> |
<UL> |
|
Line 184 properly on a LON-CAPA RedHat 6.2 system
|
Line 230 properly on a LON-CAPA RedHat 6.2 system
|
| Installation was simply a matter of following the instructions |
Installation was simply a matter of following the instructions |
| and typing the several "make" commands for each |
and typing the several "make" commands for each |
| </P> |
</P> |
| |
</FONT> |
| <H2>Configuration (automated)</H2> |
<H2>Configuration (automated)</H2> |
| <P> |
<P> |
| Not yet developed. This will be part of an interface |
Not yet developed. This will be part of an interface |
![[BACK]](/icons/back.gif){kind=icon}
Return to loncapasqldatabase.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [LON-CAPA] / doc / build