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

[raeburn]

raeburn		Sat Jul 11 04:28:32 2026 EDT

  Modified files:              
    /loncom/html/adm/help/tex	Domain_Configuration_Network_SSL.tex 
  Log:
  - Escape underscores so Domain Coordination manual can be built.
  
  
Index: loncom/html/adm/help/tex/Domain_Configuration_Network_SSL.tex
diff -u loncom/html/adm/help/tex/Domain_Configuration_Network_SSL.tex:1.1 loncom/html/adm/help/tex/Domain_Configuration_Network_SSL.tex:1.2
--- loncom/html/adm/help/tex/Domain_Configuration_Network_SSL.tex:1.1	Thu Jul  9 21:04:17 2026
+++ loncom/html/adm/help/tex/Domain_Configuration_Network_SSL.tex	Sat Jul 11 04:28:32 2026
@@ -56,7 +56,7 @@
 \end{itemize}
 
 The ``internet domain'' is the last item in each server's colon-separated entry 
-in /home/httpd/lonTabs/dns_hosts.tab. Typically servers belonging to different
+in /home/httpd/lonTabs/dns\_hosts.tab. Typically servers belonging to different
 domains, but sharing the same ``internet domain'', are LON-CAPA domains housed
 at the same institution.  For example, the ``internet domain'' of msu.edu is
 shared by three domains: msu, msudemo, and msuk12.
@@ -76,7 +76,7 @@
 Creation of the Private key and each Certificate Signing Request (CSR) for a 
 server's ``Connections Certificate'' and ``Replication Certificate'' occur when 
 ./UPDATE is run to install or update LON-CAPA.  There is also a perl script:
-/home/httpd/lonCerts/manage_ssl_certs.pl which can be run (by root) to achieve
+/home/httpd/lonCerts/manage\_ssl\_certs.pl which can be run (by root) to achieve
 the same.
 
 In both cases the CSRs are sent to certificate at loncapa.org for signing by the