--- doc/build/Attic/upgrade.html 2001/04/18 15:55:19 1.6
+++ doc/build/Attic/upgrade.html 2002/05/01 22:16:30 1.13
@@ -1,87 +1,68 @@
+
LON-CAPA Upgrade
+
+
-LON-CAPA Upgrade
-Current Upgrade Procedure
+
+
-Scott Harrison
+There are three steps for upgrading the software on your LON-CAPA server.
+
+
+
+
+
+Upgrading LON-CAPA files
-Last updated: 4/18/2001
+Download the most current
+
+loncapa.tar.gz.
-LON-CAPA system releases currently are not released under version
-numbers given the fast pace of system development. To upgrade your
-system, you need to
-
-- Make sure your software packages are up-to-date
-(based on install.lon-capa.org).
-
-- As root, run the script /usr/sbin/loncapaverifypackages.
-If packages are out-of-date, this script will output
-the out-of-date packages. Packages that this script identifies as
-"should not be here", are packages that you may wish to remove to
-improve system security. (These packages may represent important
-modifications of your institution, so do with care. Removing
-packages is done with the command: rpm -e --nodeps PACKAGE_NAME.
-
-- Upgrade old software packages.
-
-- Upgrade software packages by either
-
-- Running /usr/sbin/loncapaupgradepackages.
-- Or, going to http://install.lon-capa.org/3.1/SupplementalRPMS/,
-you can individually download each package from the world-wide web. You
-then need to enter the command:
-rpm -Uvh --force PACKAGE_RPM_FILE_NAME to upgrade your system
-for each package.
-
-
-- Make the LON-CAPA base files up to date (based on
-install.lon-capa.org).
-
-- [optional] Run the script
-/usr/sbin/loncapaverifybasepackage. Then view
-/home/httpd/html/dev/index.html for the verification report.
-If there are no real changes, then you do not need to make your files
-up-to-date.
-- Download the most recent LON-CAPA rpm (
-LON-CAPA-base-3.1-1.i386.rpm). rpm -Uvh --force LON-CAPA-base-3.1-1.i386.rpm will upgrade your software package files.
-
-- Restore configuration files.
-
-- As you run /usr/sbin/loncapaupgradepackages or enter in
-rpm -Uvh --force commands, you may
-see messages appear on your screen such as:
-
warning: /etc/httpd/conf/access.conf saved as
-/etc/httpd/conf/access.conf.rpmsave
-
You can probably just type in commands like:
-
cp /etc/httpd/conf/access.conf.rpmsave
-/etc/httpd/conf/access.conf
-
to restore your configurations. However, it is worthwhile to use the
-'diff' command to make sure that you are not accidentally losing important
-updates to the configuration files.
- - Alternatively, you can run /usr/sbin/loncaparestoreconfigurations
-to "smartly" run through the system and restore LON-CAPA configuration
-values.
-
-- Restart the LON-CAPA networking processes
-
-- /etc/rc.d/init.d/loncontrol restart
-
- - Should you wish to automate the updating of your LON-CAPA base files, you can (at your own risk) run a script which will
-do all of this automatically. You can run this script by entering the command:
-/usr/sbin/loncapaautoupgrade
-
-
-Future Upgrade Procedure (not yet implemented)
-
-In the future, LON-CAPA will be a versioned system that is released via CD.
-The upgrade procedure will be to insert the CD and follow instructions. The CD
-upgrade procedure is already defined and somewhat implemented, but awaits
-completion.
+The UPDATE command will refresh your filesystem with all
+the latest LON-CAPA software.
+
+
+
+Checking your Linux RPMs
+
+The CHECKRPMS command will check the RPMs on your machine
+against an FTP repository.
+
+
+
+Testing to see if the LON-CAPA server is operational
+
+The TEST command will check the installation software,
+the perl libraries on your system, the MySQL database, and
+will also automatically test the real-time operation of the
+LON-CAPA Apache web server.
+
+
+
+Using the TEST command will likely
+be an iterative process.
+It is normal to expect that the TEST command
+will recommend you perform various steps to ensure optimal
+performance of your LON-CAPA server.
+