[LON-CAPA-cvs] cvs: loncom /html/adm/help/tex Domain_Configuration_Quotas.tex Institutional_Integration_CAS.tex

[raeburn]

raeburn		Fri Jan 10 17:24:42 2020 EDT

  Modified files:              
    /loncom/html/adm/help/tex	Domain_Configuration_Quotas.tex 
                             	Institutional_Integration_CAS.tex 
  Log:
  - Escape underscores so Domain Coordination manual can be built.
  
  
Index: loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex
diff -u loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex:1.7 loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex:1.8
--- loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex:1.7	Fri Dec  1 20:57:35 2017
+++ loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex	Fri Jan 10 17:24:42 2020
@@ -39,7 +39,7 @@
 The user will be prompted to enter his/her username (this will be the LON-CAPA username
 or username,domain if the access is for a co-author with a domain different 
 to that of the author), and the user's LON-CAPA password. webDAV also requires that the
-dav and dav_fs modules are enabled in Apache. The way those are enabled depends on the 
+dav and dav\_fs modules are enabled in Apache. The way those are enabled depends on the 
 Linux distro (command line access required).
 the Apache config.  
 
@@ -57,12 +57,12 @@
 
 \item Ubuntu
 
-Use the commands: a2enmod dav and a2enmod dav_fs to enable the modules. 
+Use the commands: a2enmod dav and a2enmod dav\_fs to enable the modules. 
 
 \item SLES
 
-The APACHE_MODULES entry in /etc/sysconfig/apache2 contains the list of modules to be
-loaded. If dav and dav_fs are not present they should be added to the list.
+The APACHE\_MODULES entry in /etc/sysconfig/apache2 contains the list of modules to be
+loaded. If dav and dav\_fs are not present they should be added to the list.
 
 \end{itemize}
 
Index: loncom/html/adm/help/tex/Institutional_Integration_CAS.tex
diff -u loncom/html/adm/help/tex/Institutional_Integration_CAS.tex:1.3 loncom/html/adm/help/tex/Institutional_Integration_CAS.tex:1.4
--- loncom/html/adm/help/tex/Institutional_Integration_CAS.tex:1.3	Sun Dec 30 13:47:39 2018
+++ loncom/html/adm/help/tex/Institutional_Integration_CAS.tex	Fri Jan 10 17:24:42 2020
@@ -3,7 +3,7 @@
 The procedure for enabling institutional Single Sign On (SSO) via a central authentication 
 service (CAS) that is not Shibboleth involves building or installing a CAS Apache module. 
 That module might be a home-grown CAS-type module provided by your institution, or it might be 
-the standard mod_auth_cas module, available from the Apereo CAS project (see:
+the standard mod\_auth\_cas module, available from the Apereo CAS project (see:
 https://github.com/apereo/mod\_auth\_cas ). In addition, you will need to modify the Apache 
 configuration for your LON-CAPA server to (a) load the module, and (b) configure LON-CAPA
 to use it, by default, when unauthenticated users access /adm/roles.