--- doc/build/Attic/reconfig.html	2002/04/23 12:06:28	1.8
+++ doc/build/Attic/reconfig.html	2002/07/27 23:08:10	1.11
@@ -1,70 +1,112 @@
-<!-- $Id: reconfig.html,v 1.8 2002/04/23 12:06:28 harris41 Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!-- $Id: reconfig.html,v 1.11 2002/07/27 23:08:10 harris41 Exp $ -->
 <html>
 <head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></meta>
 <title>Configuration of a LON-CAPA Server</title>
 <!-- pdfahref index.pdf -->
 <!-- button CONFIGURE -->
 </head>
-<body bgcolor='#ffffff'>
+<body bgcolor="#ffffff">
 <!-- preamble start -->
 <p>
 There are about a dozen files on the LON-CAPA server systems
-which customize how each system interacts with the rest of the
-LON-CAPA network.
+which the system administrator may need to adjust.
 </p>
 <p>
 The two most important configuration files are:
+</p>
 <ul>
 <li><strong>loncapa.conf</strong> -
-typically located in the directory <tt>/etc/httpd/conf/</tt>
-<br /><i>contains variables and modifications necessary for
-the effective running of the Apache web server</i>
+typically located in the directory <tt>/etc/httpd/conf/</tt>;
+<br /><i>contains machine-specific and institution-specific
+variables and modifications necessary for
+the effective running of the Apache web server;
+note that there is also a <strong>loncapa_apache.conf</strong>
+which should be installed, but not modified</i>
 <br />&nbsp;
 </li>
 <li><strong>hosts.tab</strong> -
-typically located in the directory <tt>/home/httpd/lonTabs/</tt>
+typically located in the directory <tt>/home/httpd/lonTabs/</tt>;
 <br /><i>is a listing of all other internet machines that a server
 system considers to be valid server systems on the LON-CAPA
 network</i>
 <br />&nbsp;
 </li>
 </ul>
-</p>
-</font>
 <!-- preamble end -->
 <!-- maintext start -->
-<h3>Configuration files and examples</h3>
-LON-CAPA currently depends on the following list of configuration
-files.  Locations of these files are by default.  Depending on your
-Linux distribution (RedHat, Mandrake, Debian, etc.), the file paths
+<h3>Current Reconfiguration Procedure</h3>
+<p>
+After making any configuration change, you will need to restart system
+services.  The two most important system services on a LON-CAPA system are
+<strong>loncapa</strong> and <strong>httpd</strong>.  Here are the
+commands for restarting the system services:
+</p>
+<table bgcolor="#aaaaaa" border="1"><tr><td>
+<tt>/etc/rc.d/init.d/loncapa restart</tt>
+<br /><tt>/etc/rc.d/init.d/httpd restart</tt>
+</td></tr></table>
+<p>
+We recommend that a knowledgeable system administrator should
+perform any adjustments on a LON-CAPA server machine.
+Locations of these files are by default.  Depending on your
+Linux distribution--RedHat, Mandrake, Debian, etc, the file paths
 may be elsewhere.
+</p>
+<h3>Configuration files that will have to be altered</h3>
+<p>
+LON-CAPA currently depends on the following list of configuration
+files.  Note that <tt>loncapa.conf</tt> is automatically
+altered by the installation/upgrade scripts associated with
+the tarball-distribution (see the <b>INSTALL</b> and <b>UPGRADE</b>
+sections of this web-site).  (Thus, the system administrator should
+not have to further adjust <tt>loncapa.conf</tt> from the terminal.)
+</p>
 <ul>
-<li><a href='confexamples/krb.conf'>[EXAMPLE]</a> /etc/krb.conf</li>
-<li><a href='confexamples/access.conf'>[EXAMPLE]</a>
-/etc/httpd/conf/access.conf</li>
-<li><a href='confexamples/loncapa.conf'>[EXAMPLE]</a>
+<li><a href="confexamples/loncapa.conf">[EXAMPLE]</a>
 /etc/httpd/conf/loncapa.conf</li>
-<li><a href='confexamples/hosts.tab'>[EXAMPLE]</a>
+<li><a href="confexamples/hosts.tab">[EXAMPLE]</a>
 /home/httpd/lonTabs/hosts.tab</li>
-<li><a href='confexamples/spare.tab'>[EXAMPLE]</a>
+<li><a href="confexamples/spare.tab">[EXAMPLE]</a>
 /home/httpd/lonTabs/spare.tab</li>
-<li><a href='confexamples/htpasswd'>[EXAMPLE]</a>
+<li><a href="confexamples/krb.conf">[EXAMPLE]</a> /etc/krb.conf</li>
+<li><a href="confexamples/htpasswd">[EXAMPLE]</a>
 /home/httpd/lonTabs/htpasswd</li>
-<li><a href='confexamples/smb.conf'>[EXAMPLE]</a> /etc/smb.conf</li>
-<li><a href='confexamples/ntp.conf'>[EXAMPLE]</a> /etc/ntp.conf</li>
-<li><a href='confexamples/un_keyword.tab'>[EXAMPLE]</a>
-/home/httpd/html/res/adm/includes/un_keyword.tab</li>
-<li><a href='confexamples/step-tickers'>[EXAMPLE]</a>
+<li><a href="confexamples/ntp.conf">[EXAMPLE]</a> /etc/ntp.conf</li>
+<li><a href="confexamples/step-tickers">[EXAMPLE]</a>
 /etc/ntp/step-tickers</li>
-<li><a href='confexamples/pwauth'>[EXAMPLE]</a> /etc/pam.d/pwauth</li>
-<li><a href='confexamples/config'>[EXAMPLE]</a> /etc/atalk/config</li>
+<li><a href="confexamples/pwauth">[EXAMPLE]</a> /etc/pam.d/pwauth</li>
 </ul>
-<h3>Current Reconfiguration Procedure</h3>
+<h3>Configuration files that do not have to be altered</h3>
 <p>
-We recommend that you handle the reconfiguration manually.
-A knowledgeable system administrator should alter these configuration
-files.
+The following configuration files are critical for the correct
+performance of a LON-CAPA server machine.  Typically, these configuration
+files do not need to be adjusted by the system administrator.
 </p>
+<ul>
+<li><a href="confexamples/loncapa_apache.conf">[EXAMPLE]</a>
+/etc/httpd/conf/loncapa_apache.conf</li>
+<li><a href="confexamples/un_keyword.tab">[EXAMPLE]</a>
+/home/httpd/html/res/adm/includes/un_keyword.tab</li>
+</ul>
+
+<h3>Configuring Secondary Services</h3>
+<p>
+LON-CAPA does not provide integrated support for secondary services.
+The expectation is that knowledgeable system administrators will
+customize these secondary services for their institution.
+</p>
+<p>
+We do, however, provide example configurations of services that you
+may want to deliver with LON-CAPA (i.e. Samba and AppleChooser).
+</p>
+<ul>
+<li><a href="confexamples/smb.conf">[EXAMPLE]</a> /etc/smb.conf</li>
+<li><a href="confexamples/config">[EXAMPLE]</a> /etc/atalk/config</li>
+</ul>
 <!-- maintext end -->
+<!-- validated -->
 </body>
 </html>
