$Id: shortest_path_redhat7.2.txt,v 1.2 2002/04/17 00:06:32 harris41 Exp $
INSTALLING LON-CAPA ON A REDHAT 7.2 SYSTEM
* Quick Instructions
* System Requirements
PLEASE contact email@example.com if these instructions
do not work.
PLEASE subscribe yourself to the ANNOUNCE MAILING LIST!
Go to http://mail.lon-capa.org/mailman/listinfo/lon-capa-announce
1. Download http://install.lon-capa.org/versions/current/loncapa.tar.gz
(from a linux terminal, type
2. tar xzvf loncapa.tar.gz
3. cd loncapa
4. Read the README file (this file).
5. EXECUTE: ./UPDATE
6. EXECUTE: ./TEST
Please follow the instructions that are given
to you by the TEST command. You will probably
have to make a few changes and continue to run
TEST until all the system-critical steps are
taken care of.
LON-CAPA is a GPL-based project which originally was, and in a
significant sense still is, located at Michigan State University.
The installation, software versioning, and specification is
currently maintained by the freeware community which includes
the author of this document and more importantly you!
Your interest, questions and suggestions are enthusiastically
invited for the specific development of the GPL code.
We do our best to help get you started with a 100% operational
system. Please e-mail firstname.lastname@example.org or email@example.com
for help with software installation.
For full-time, classroom usage, an adequate LON-CAPA server
* a multiprocessor machine,
* a CPU speed of 1 gigahertz,
* a gigabyte of memory,
* and at least 40 to 80 gigabytes of hard disk space.
A lesser machine can be used for toying around with LON-CAPA
(LON-CAPA will run for a single user on most any machine).
LON-CAPA servers experience significant peaks of activity
before a homework submission deadline. To support these critical
peaks of activity, it is strongly advised that LON-CAPA machines
fit the above recommendation.
If thousands of students start accessing the box as a web server...
well you may want to consider more options. The design of the LON-CAPA
system is to naturally and transparently load-balance on multiple
computer clusters. So, a simple solution for running an entire
college campus is to just have an adequate plurality of LON-CAPA
servers rather than a single, particularly monstrous server.
We like to think of high web server usage as "a good problem" though.. :)
More Information on Hardware and System Administration
I find that LON-CAPA works nicely (for development purposes)
on a Pentium II, 20 gigabytes of hard-disk space, 256M RAM,
and 400MHz. The consensus is though, that this may only
be adequate for a class of a dozen students.
If you are making a serious investment, we suggest you
join our mailing list by visiting
By posting to this mailing list, you can learn about what
solutions have worked for others.
LON-CAPA works on any Intel-based RedHat-compatible
hardware. Unlike other software systems, it works
comparatively well on dusty old crippled machines without
much RAM or processing.
We support Linux OS. LON-CAPA has been shown to work on Debian,
Mandrake, and RedHat. Instructions are based on RedHat-centric
installs. Given the current level of new LON-CAPA feature requests
and frequency of new software versions, we suggest that you stick
with RedHat to reduce high-frequency system administration overhead.
*** PERL ***
It is important to check and see if your system has all
needed perl modules in /usr/lib/perl5/.
*** RPMS ***
It is important to:
* keep your RPMs up to date
* try to have a reasonably minimal set
*** MYSQL ***
It should be kept operational at all times.
In case of failure, there is a resynchronizing
strategy so that the data on the filesystem
continually refreshes the data within the
*** APACHE ***
LON-CAPA expects that conf/loncapa.conf will be the
last Apache configuration file to be processed before
launching the httpd server. This may interfere
with other ways in which you utilize your web server.
For instance, LON-CAPA requires that httpd
run as user=www and group=www.
3. Web Layer
4. File Status
5. RPM Status
Many thanks to Matthew Hall (Michigan State University),
Guy Albertelli (Michigan State University), Felicia
Berryman (Michigan State University), Gerd Kortemeyer
(Michigan State University) and Martin Siegert (Simon
Frasier University) for their responsive feedback regarding
ideas in this document.