[deployment-guide/comm-rel: 7/26] Removed all index terms as I am going to rewrite them anyway.

[dsilas]

commit ae53d27bee0f90918783d2ba509a8fa1e8268e96
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Sat Jun 12 01:33:54 2010 +0200

    Removed all index terms as I am going to rewrite them anyway.

 en-US/Controlling_Access_to_Services.xml |   48 ------------------------------
 1 files changed, 0 insertions(+), 48 deletions(-)
---
diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml
index 02a268f..eb604a0 100644
--- a/en-US/Controlling_Access_to_Services.xml
+++ b/en-US/Controlling_Access_to_Services.xml
@@ -4,15 +4,6 @@
 <chapter
   id="ch-Controlling_Access_to_Services">
   <title>Controlling Access to Services</title>
-  <indexterm
-    significance="normal">
-    <primary>services</primary>
-    <secondary>controlling access to</secondary>
-  </indexterm>
-  <indexterm
-    significance="normal">
-    <primary>security</primary>
-  </indexterm>
   <para>Maintaining security on your system is extremely important, and one approach for this task is to manage access to system services carefully. Your system may need to provide open access to particular services (for example, <command>httpd</command> if you are running a Web server). However, if you do not need to provide a service, you should turn it off to minimize your exposure to possible bug exploits.</para>
   <para>There are several different methods for managing access to system services. <!-- RHEL5:  Decide  -->Choose which method of management to use based on the service, your system's configuration, and your level of Linux expertise.</para>
   <para>The easiest way to deny access to a service is to turn it off. Both the services managed by <command>xinetd</command> and the services in the <filename>/etc/rc.d/init.d</filename> hierarchy (also known as SysV services) can be configured to start or stop using three different applications:</para>
@@ -58,10 +49,6 @@
   <section
     id="s1-services-runlevels">
     <title>Runlevels</title>
-    <indexterm
-      significance="normal">
-      <primary>runlevels</primary>
-    </indexterm>
     <para>Before you can configure access to services, you must understand Linux runlevels. A runlevel is a state, or <firstterm>mode</firstterm>, that is defined by the services listed in the directory <filename>/etc/rc.d/rc<replaceable>&lt;x&gt;</replaceable>.d</filename>, where <replaceable>&lt;x&gt;</replaceable> is the number of the runlevel.</para>
     <para>The following runlevels exist:</para>
     <itemizedlist>
@@ -96,10 +83,6 @@
     id="s1-services-tcp-wrappers">
     <title>TCP Wrappers</title>
     <para>
-      <indexterm
-        significance="normal">
-        <primary>TCP wrappers</primary>
-      </indexterm>
        Many UNIX system administrators are accustomed to using TCP wrappers to manage access to certain network services. Any network services managed by <command>xinetd</command> (as well as any program with built-in support for <command>libwrap</command>) can use TCP wrappers to manage access. <command>xinetd</command> can use the <filename>/etc/hosts.allow</filename> and <filename>/etc/hosts.deny</filename> files to configure access to system services. As the names imply, <filename>hosts.allow</filename> contains a list of rules that allow clients to access the network services controlled by <command>xinetd</command>, and <filename>hosts.deny</filename> contains rules to deny access. The <filename>hosts.allow</filename> file takes precedence over the <filename>hosts.deny</filename> file. Permissions to grant or deny access can be based on individual IP address (or hostnames) or on a pattern of clients. Refer to <filename>hosts_access</filename> in section 5 of the man pag
 es (<command>man 5 hosts_access</command>) for details.</para>
     <!-- RHEL5:   REMOVING CROSS LINK
     <para>For more information on using TCP Wrappers, refer to <xref linkend="s1-tcpwrappers-purpose"/>.</para>
@@ -109,19 +92,6 @@
       <title>
         <command>xinetd</command>
       </title>
-      <indexterm
-        significance="normal">
-        <primary>
-          <command>xinetd</command>
-        </primary>
-      </indexterm>
-      <indexterm
-        significance="normal">
-        <primary>TCP wrappers</primary>
-        <secondary>
-          <command>xinetd</command>
-        </secondary>
-      </indexterm>
       <para>To control access to Internet services, use <command>xinetd</command>, which is a secure replacement for <command>inetd</command>. The <command>xinetd</command> daemon conserves system resources, provides access control and logging, and can be used to start special-purpose servers. <command>xinetd</command> can also be used to grant or deny access to particular hosts, provide service access at specific times, limit the rate of incoming connections, limit the load created by connections, and more.</para>
       <para>
         <command>xinetd</command> runs constantly and listens on all ports for the services it manages. When a connection request arrives for one of its managed services, <command>xinetd</command> starts up the appropriate server for that service.</para>
@@ -136,12 +106,6 @@
     <title>
       <application>Services Configuration Tool</application>
     </title>
-    <indexterm
-      significance="normal">
-      <primary>
-        <application>Services Configuration Tool</application>
-      </primary>
-    </indexterm>
     <para>The <application>Services Configuration Tool</application> is a graphical application developed by Red Hat to configure which SysV services in the <filename>/etc/rc.d/init.d</filename> directory are started at boot time (for runlevels 3, 4, and 5) and which <command>xinetd</command> services are enabled. It also allows you to start, stop, and restart SysV services as well as <!-- RHEL5:  restart --> reload <command>xinetd</command>.</para>
     <para>To start the <application>Services Configuration Tool</application> from the desktop, go to the Applications (the main menu on the panel) &gt; <guimenu>System Settings</guimenu> &gt; <guimenu>Server Settings</guimenu> &gt; <guimenuitem>Services</guimenuitem> or type the command <command>system-config-services</command> at a shell prompt (for example, in an <application>XTerm</application> or a <application>GNOME terminal</application>).</para>
     <figure
@@ -195,12 +159,6 @@
     <title>
       <application>ntsysv</application>
     </title>
-    <indexterm
-      significance="normal">
-      <primary>
-        <application>ntsysv</application>
-      </primary>
-    </indexterm>
     <para>The <application>ntsysv</application> utility provides a simple interface for activating or deactivating services. You can use <application>ntsysv</application> to turn an <command>xinetd</command>-managed service on or off. You can also use <application>ntsysv</application> to configure runlevels. By default, only the current runlevel is configured. To configure a different runlevel, specify one or more runlevels with the <option>--level</option> option. For example, the command <command>ntsysv --level 345</command> configures runlevels 3, 4, and 5.</para>
     <para>The <application>ntsysv</application> interface works like the text mode installation program. Use the up and down arrows to navigate up and down the list. The space bar selects/unselects services and is also used to "press" the <guilabel>Ok</guilabel> and <guilabel>Cancel</guilabel> buttons. To move between the list of services and the <guilabel>Ok</guilabel> and <guilabel>Cancel</guilabel> buttons, use the <keycap>Tab</keycap> key. An asterisk (<guilabel>*</guilabel>) signifies that a service is set to on. Pressing the <keycap>F1</keycap> key displays a short description of the selected service.</para>
     <!-- RHEL5:   ddomingo at redhat.com: added PNG image     -->
@@ -229,12 +187,6 @@
     <title>
       <command>chkconfig</command>
     </title>
-    <indexterm
-      significance="normal">
-      <primary>
-        <command>chkconfig</command>
-      </primary>
-    </indexterm>
     <para>The <command>chkconfig</command> command can also be used to activate and deactivate services. The <command>chkconfig --list</command> command displays a list of system services and whether they are started (<command>on</command>) or stopped (<command>off</command>) in runlevels 0-6. At the end of the list is a section for the services managed by <command>xinetd</command>.</para>
     <para>If the <command>chkconfig --list</command> command is used to query a service managed by <command>xinetd</command>, it displays whether the <command>xinetd</command> service is enabled (<command>on</command>) or disabled (<command>off</command>). For example, the command <command>chkconfig --list rsync</command> returns the following output:</para>
     <screen>rsync on</screen>