[deployment-guide/comm-rel: 8/26] Changed the structure of the chapter.
dsilas
dsilas at fedoraproject.org
Mon Jun 21 11:42:13 UTC 2010
commit 2e1712b2c624a9083806394c101ce9f605ade31f
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Sat Jun 12 02:25:41 2010 +0200
Changed the structure of the chapter.
No new content written yet, I just wanted to make the chapter easier to
navigate (both for future readers and me).
en-US/Controlling_Access_to_Services.xml | 228 ++++++++++++++----------------
1 files changed, 107 insertions(+), 121 deletions(-)
---
diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml
index eb604a0..23ff981 100644
--- a/en-US/Controlling_Access_to_Services.xml
+++ b/en-US/Controlling_Access_to_Services.xml
@@ -1,8 +1,7 @@
<?xml version='1.0'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<chapter
- id="ch-Controlling_Access_to_Services">
+<chapter id="ch-Controlling_Access_to_Services">
<title>Controlling Access to Services</title>
<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>
@@ -46,9 +45,8 @@
<title>Important</title>
<para>When you allow access for new services, always remember that both the firewall and SELinux need to be configured as well. One of the most common mistakes committed when configuring a new service is neglecting to implement the necessary firewall configuration and SELinux policies to allow access for it. Refer to <!-- TBD6: <xref linkend="s1-basic-firewall"/> --> for more information.</para>
</important>
- <section
- id="s1-services-runlevels">
- <title>Runlevels</title>
+ <section id="s1-services-runlevels">
+ <title>Configuring the Default Runlevel</title>
<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><x></replaceable>.d</filename>, where <replaceable><x></replaceable> is the number of the runlevel.</para>
<para>The following runlevels exist:</para>
<itemizedlist>
@@ -79,19 +77,112 @@
<screen>id:5:initdefault:</screen>
<para>Change the number in this line to the desired runlevel. The change does not take effect until you reboot the system.</para>
</section>
- <section
- id="s1-services-tcp-wrappers">
- <title>TCP Wrappers</title>
+ <section id="s1-services-services">
+ <title>Configuring Running Services</title>
+ <section id="s2-services-serviceconf">
+ <title>Using <application>Service Configuration</application> tool</title>
+ <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) > <guimenu>System Settings</guimenu> > <guimenu>Server Settings</guimenu> > <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
+ float="0"
+ id="fig-serviceconf">
+ <title>
+ <application>Services Configuration Tool</application>
+ </title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/serviceconf.png"
+ format="PNG"
+ scalefit="1"/>
+ </imageobject>
+ <textobject>
+ <para>Configuring network services</para>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <para>The <application>Services Configuration Tool</application> displays the current runlevel as well as the runlevel you are currently editing. To edit a different runlevel, select <guimenu>Edit Runlevel</guimenu> from the pulldown menu and select runlevel 3, 4, or 5. Refer to <xref
+ linkend="s1-services-runlevels"/> for a description of runlevels.</para>
+ <para>The <application>Services Configuration Tool</application> lists the services from the <filename>/etc/rc.d/init.d</filename> directory as well as the services controlled by <command>xinetd</command>. Click on the name of the service from the list on the left-hand side of the application to display a brief description of that service as well as the status of the service. If the service is not an <command>xinetd</command> service, the status window shows whether the service is currently running. If the service is controlled by <command>xinetd</command>, the status window displays the phrase <guilabel>xinetd service</guilabel>.</para>
+ <para>To start, stop, or restart a service immediately, select the service from the list and click the appropriate button on the toolbar (or choose the action from the <guimenu>Actions</guimenu> pulldown menu). If the service is an <command>xinetd</command> service, the action buttons are disabled because they cannot be started or stopped individually.</para>
+ <para>If you enable/disable an <command>xinetd</command> service by checking or unchecking the checkbox next to the service name, you must select <guimenu>File</guimenu> > <guimenuitem>Save Changes</guimenuitem> from the pulldown menu (or the <guimenuitem>Save</guimenuitem> button above the tabs) to <!-- RHEL5: restart -->reload <command>xinetd</command> and immediately enable/disable the <command>xinetd</command> service that you changed. <command>xinetd</command> is also configured to remember the setting. You can enable/disable multiple <command>xinetd</command> services at a time and save the changes when you are finished.</para>
+ <para>For example, assume you check <command>rsync</command> to enable it in runlevel 3 and then save the changes. The <command>rsync</command> service is immediately enabled. The next time <command>xinetd</command> is started, <command>rsync</command> is still enabled.</para>
+ <note>
+ <title>Note</title>
+ <para>When you save changes to <command>xinetd</command> services, <command>xinetd</command> is <!-- RHEL5: restarted -->reloaded, and the changes take place immediately. When you save changes to other services, the runlevel is reconfigured, but the changes do not take effect immediately.</para>
+ </note>
+ <para>To enable a non-<command>xinetd</command> service to start at boot time for the currently selected runlevel, check the <!-- RHEL5: check -->box beside the name of the service in the list. After configuring the runlevel, apply the changes by selecting <guimenu>File</guimenu> > <guimenuitem>Save Changes</guimenuitem> from the pulldown menu. The runlevel configuration is changed, but the runlevel is not restarted; thus, the changes do not take place immediately.</para>
+ <para>For example, assume you are configuring runlevel 3. If you change the value for the <command>httpd</command> service from checked to unchecked and then select <guimenuitem>Save Changes</guimenuitem>, the runlevel 3 configuration changes so that <command>httpd</command> is not started at boot time. However, runlevel 3 is not reinitialized, so <command>httpd</command> is still running. Select one of following options at this point:</para>
+ <orderedlist
+ continuation="restarts"
+ inheritnum="ignore">
+ <listitem>
+ <para>Stop the <command>httpd</command> service — Stop the service by selecting it from the list and clicking the <guibutton>Stop</guibutton> button. A message appears stating that the service was stopped successfully.</para>
+ </listitem>
+ <listitem>
+ <para>Reinitialize the runlevel — Reinitialize the runlevel by going to a shell prompt and typing the command <command>telinit <replaceable>x</replaceable>
+ </command> (where <replaceable>x</replaceable> is the runlevel number; in this example, 3.). This option is recommended if you change the <guilabel>Start at Boot</guilabel> value of multiple services and want to activate the changes immediately.</para>
+ </listitem>
+ <listitem>
+ <para>Do nothing else — You do not have to stop the <command>httpd</command> service. You can wait until the system is rebooted for the service to stop. The next time the system is booted, the runlevel is initialized without the <command>httpd</command> service running.</para>
+ </listitem>
+ </orderedlist>
+ <para>To add a service to a runlevel, select the runlevel from the <guimenu>Edit Runlevel</guimenu> pulldown menu, and then select <guimenu>Actions</guimenu> > <guimenuitem>Add Service</guimenuitem>. To delete a service from a runlevel, select the runlevel from the <guimenu>Edit Runlevel</guimenu> pulldown menu, select the service to be deleted from the list on the left, and select <guimenu>Actions</guimenu> > <guimenuitem>Delete Service</guimenuitem>.</para>
+ </section>
+ <section id="s2-services-chkconfig">
+ <title>Using <command>chkconfig</command></title>
+ <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>
+ <para>As shown, <command>rsync</command> is enabled as an <command>xinetd</command> service. If <command>xinetd</command> is running, <command>rsync</command> is enabled.</para>
+ <para>If you use <command>chkconfig --list</command> to query a service in <filename>/etc/rc.d</filename>, that service's settings for each runlevel are displayed. For example, the command <command>chkconfig --list httpd</command> returns the following output:</para>
+ <screen>httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off</screen>
+ <para>
+ <command>chkconfig</command> can also be used to configure a service to be started (or not) in a specific runlevel. For example, to turn <command>nscd</command> off in runlevels 3, 4, and 5, use the following command:</para>
+ <screen>
+ <command>chkconfig --level 345 nscd off</command>
+ </screen>
+ <warning>
+ <title>Warning</title>
+ <para>Services managed by <command>xinetd</command> are immediately affected by <command>chkconfig</command>. For example, if <command>xinetd</command> is running while <command>rsync</command> is disabled, and the command <command>chkconfig rsync on</command> is executed, then <command>rsync</command> is immediately enabled without having to restart <command>xinetd</command> manually. Changes for other services do not take effect immediately after using <command>chkconfig</command>. You must stop or start the individual service with the command <command>service <replaceable><daemon></replaceable> stop</command> (where <replaceable><daemon></replaceable> is the name of the service you want to stop; for example, <command>httpd</command>). Replace <command>stop</command> with <command>start</command> or <command>restart</command> to start or restart the service.</para>
+ </warning>
+ </section>
+ <section id="s2-services-ntsysv">
+ <title>Using <application>ntsysv</application></title>
+ <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 -->
+ <figure
+ float="0"
+ id="fig-ntsysv">
+ <title>The <application>ntsysv</application> utility</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/ntsysv.png"
+ format="PNG"/>
+ </imageobject>
+ <textobject>
+ <para>The <application>ntsysv</application> utility</para>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <warning>
+ <title>Warning</title>
+ <para>Services managed by <command>xinetd</command> are immediately affected by <application>ntsysv</application>. For all other services, changes do not take effect immediately. You must stop or start the individual service with the command <command>service <replaceable><daemon></replaceable> stop</command> (where <replaceable><daemon></replaceable> is the name of the service you want to stop; for example, <command>httpd</command>). Replace <command>stop</command> with <command>start</command> or <command>restart</command> to start or restart the service.</para>
+ </warning>
+ </section>
+
+ </section>
+ <section id="s1-services-tcp-wrappers">
+ <title>Configuring TCP Wrappers</title>
<para>
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>
-->
- <section
- id="s2-services-xinetd">
- <title>
- <command>xinetd</command>
- </title>
+ <section id="s2-services-xinetd">
+ <title>Using <command>xinetd</command></title>
<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>
@@ -101,114 +192,10 @@
-->
</section>
</section>
- <section
- id="s1-services-serviceconf">
- <title>
- <application>Services Configuration Tool</application>
- </title>
- <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) > <guimenu>System Settings</guimenu> > <guimenu>Server Settings</guimenu> > <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
- float="0"
- id="fig-serviceconf">
- <title>
- <application>Services Configuration Tool</application>
- </title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/serviceconf.png"
- format="PNG"
- scalefit="1"/>
- </imageobject>
- <textobject>
- <para>Configuring network services</para>
- </textobject>
- </mediaobject>
- </figure>
- <para>The <application>Services Configuration Tool</application> displays the current runlevel as well as the runlevel you are currently editing. To edit a different runlevel, select <guimenu>Edit Runlevel</guimenu> from the pulldown menu and select runlevel 3, 4, or 5. Refer to <xref
- linkend="s1-services-runlevels"/> for a description of runlevels.</para>
- <para>The <application>Services Configuration Tool</application> lists the services from the <filename>/etc/rc.d/init.d</filename> directory as well as the services controlled by <command>xinetd</command>. Click on the name of the service from the list on the left-hand side of the application to display a brief description of that service as well as the status of the service. If the service is not an <command>xinetd</command> service, the status window shows whether the service is currently running. If the service is controlled by <command>xinetd</command>, the status window displays the phrase <guilabel>xinetd service</guilabel>.</para>
- <para>To start, stop, or restart a service immediately, select the service from the list and click the appropriate button on the toolbar (or choose the action from the <guimenu>Actions</guimenu> pulldown menu). If the service is an <command>xinetd</command> service, the action buttons are disabled because they cannot be started or stopped individually.</para>
- <para>If you enable/disable an <command>xinetd</command> service by checking or unchecking the checkbox next to the service name, you must select <guimenu>File</guimenu> > <guimenuitem>Save Changes</guimenuitem> from the pulldown menu (or the <guimenuitem>Save</guimenuitem> button above the tabs) to <!-- RHEL5: restart -->reload <command>xinetd</command> and immediately enable/disable the <command>xinetd</command> service that you changed. <command>xinetd</command> is also configured to remember the setting. You can enable/disable multiple <command>xinetd</command> services at a time and save the changes when you are finished.</para>
- <para>For example, assume you check <command>rsync</command> to enable it in runlevel 3 and then save the changes. The <command>rsync</command> service is immediately enabled. The next time <command>xinetd</command> is started, <command>rsync</command> is still enabled.</para>
- <note>
- <title>Note</title>
- <para>When you save changes to <command>xinetd</command> services, <command>xinetd</command> is <!-- RHEL5: restarted -->reloaded, and the changes take place immediately. When you save changes to other services, the runlevel is reconfigured, but the changes do not take effect immediately.</para>
- </note>
- <para>To enable a non-<command>xinetd</command> service to start at boot time for the currently selected runlevel, check the <!-- RHEL5: check -->box beside the name of the service in the list. After configuring the runlevel, apply the changes by selecting <guimenu>File</guimenu> > <guimenuitem>Save Changes</guimenuitem> from the pulldown menu. The runlevel configuration is changed, but the runlevel is not restarted; thus, the changes do not take place immediately.</para>
- <para>For example, assume you are configuring runlevel 3. If you change the value for the <command>httpd</command> service from checked to unchecked and then select <guimenuitem>Save Changes</guimenuitem>, the runlevel 3 configuration changes so that <command>httpd</command> is not started at boot time. However, runlevel 3 is not reinitialized, so <command>httpd</command> is still running. Select one of following options at this point:</para>
- <orderedlist
- continuation="restarts"
- inheritnum="ignore">
- <listitem>
- <para>Stop the <command>httpd</command> service — Stop the service by selecting it from the list and clicking the <guibutton>Stop</guibutton> button. A message appears stating that the service was stopped successfully.</para>
- </listitem>
- <listitem>
- <para>Reinitialize the runlevel — Reinitialize the runlevel by going to a shell prompt and typing the command <command>telinit <replaceable>x</replaceable>
- </command> (where <replaceable>x</replaceable> is the runlevel number; in this example, 3.). This option is recommended if you change the <guilabel>Start at Boot</guilabel> value of multiple services and want to activate the changes immediately.</para>
- </listitem>
- <listitem>
- <para>Do nothing else — You do not have to stop the <command>httpd</command> service. You can wait until the system is rebooted for the service to stop. The next time the system is booted, the runlevel is initialized without the <command>httpd</command> service running.</para>
- </listitem>
- </orderedlist>
- <para>To add a service to a runlevel, select the runlevel from the <guimenu>Edit Runlevel</guimenu> pulldown menu, and then select <guimenu>Actions</guimenu> > <guimenuitem>Add Service</guimenuitem>. To delete a service from a runlevel, select the runlevel from the <guimenu>Edit Runlevel</guimenu> pulldown menu, select the service to be deleted from the list on the left, and select <guimenu>Actions</guimenu> > <guimenuitem>Delete Service</guimenuitem>.</para>
- </section>
- <section
- id="s1-services-ntsysv">
- <title>
- <application>ntsysv</application>
- </title>
- <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 -->
- <figure
- float="0"
- id="fig-ntsysv">
- <title>The <application>ntsysv</application> utility</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/ntsysv.png"
- format="PNG"/>
- </imageobject>
- <textobject>
- <para>The <application>ntsysv</application> utility</para>
- </textobject>
- </mediaobject>
- </figure>
- <warning>
- <title>Warning</title>
- <para>Services managed by <command>xinetd</command> are immediately affected by <application>ntsysv</application>. For all other services, changes do not take effect immediately. You must stop or start the individual service with the command <command>service <replaceable><daemon></replaceable> stop</command> (where <replaceable><daemon></replaceable> is the name of the service you want to stop; for example, <command>httpd</command>). Replace <command>stop</command> with <command>start</command> or <command>restart</command> to start or restart the service.</para>
- </warning>
- </section>
- <section
- id="s1-services-chkconfig">
- <title>
- <command>chkconfig</command>
- </title>
- <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>
- <para>As shown, <command>rsync</command> is enabled as an <command>xinetd</command> service. If <command>xinetd</command> is running, <command>rsync</command> is enabled.</para>
- <para>If you use <command>chkconfig --list</command> to query a service in <filename>/etc/rc.d</filename>, that service's settings for each runlevel are displayed. For example, the command <command>chkconfig --list httpd</command> returns the following output:</para>
- <screen>httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off</screen>
- <para>
- <command>chkconfig</command> can also be used to configure a service to be started (or not) in a specific runlevel. For example, to turn <command>nscd</command> off in runlevels 3, 4, and 5, use the following command:</para>
- <screen>
-<command>chkconfig --level 345 nscd off</command>
- </screen>
- <warning>
- <title>Warning</title>
- <para>Services managed by <command>xinetd</command> are immediately affected by <command>chkconfig</command>. For example, if <command>xinetd</command> is running while <command>rsync</command> is disabled, and the command <command>chkconfig rsync on</command> is executed, then <command>rsync</command> is immediately enabled without having to restart <command>xinetd</command> manually. Changes for other services do not take effect immediately after using <command>chkconfig</command>. You must stop or start the individual service with the command <command>service <replaceable><daemon></replaceable> stop</command> (where <replaceable><daemon></replaceable> is the name of the service you want to stop; for example, <command>httpd</command>). Replace <command>stop</command> with <command>start</command> or <command>restart</command> to start or restart the service.</para>
- </warning>
- </section>
- <section
- id="s1-services-additional-resources">
+ <section id="s1-services-additional-resources">
<title>Additional Resources</title>
<para>For more information, refer to the following resources.</para>
- <section
- id="services-installed-docs">
+ <section id="services-installed-docs">
<title>Installed Documentation</title>
<itemizedlist>
<listitem>
@@ -220,8 +207,7 @@
</listitem>
</itemizedlist>
</section>
- <section
- id="services-useful-websites">
+ <section id="services-useful-websites">
<title>Useful Websites</title>
<itemizedlist>
<listitem>
More information about the docs-commits
mailing list