Return to config.frag CVS log

Up to [LON-CAPA] / doc / build

Moving to update install site.

<p>
There are about a dozen files on the LON-CAPA server systems
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 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>;
<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>
<!-- preamble end -->
<!-- maintext start -->
<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/loncapa.conf">[EXAMPLE]</a>
/etc/httpd/conf/loncapa.conf</li>
<li><a href="confexamples/hosts.tab">[EXAMPLE]</a>
/home/httpd/lonTabs/hosts.tab</li>
<li><a href="confexamples/spare.tab">[EXAMPLE]</a>
/home/httpd/lonTabs/spare.tab</li>
<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/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>
</ul>
<h3>Configuration files that do not have to be altered</h3>
<p>
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>

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.