[deployment-guide/comm-rel: 11/26] Updated the Service Tool section.
dsilas
dsilas at fedoraproject.org
Mon Jun 21 11:42:28 UTC 2010
commit 89e73646c654a2d27b5f5aa92aeb00349e7361b9
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Tue Jun 15 08:43:31 2010 +0200
Updated the Service Tool section.
en-US/Controlling_Access_to_Services.xml | 236 ++++++++++++++++----
...ntrolling-access-to-services-authentication.png | Bin 0 -> 19489 bytes
...ng-access-to-services-service_configuration.png | Bin 0 -> 146999 bytes
...rolling-access-to-services-service_disabled.png | Bin 0 -> 864 bytes
...trolling-access-to-services-service_enabled.png | Bin 0 -> 912 bytes
...trolling-access-to-services-service_running.png | Bin 0 -> 707 bytes
...rolling-access-to-services-service_selected.png | Bin 0 -> 617 bytes
...trolling-access-to-services-service_stopped.png | Bin 0 -> 734 bytes
...trolling-access-to-services-service_unknown.png | Bin 0 -> 725 bytes
...ontrolling-access-to-services-service_wrong.png | Bin 0 -> 697 bytes
en-US/images/serviceconf.png | Bin 27775 -> 0 bytes
11 files changed, 189 insertions(+), 47 deletions(-)
---
diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml
index 56439ef..9950012 100644
--- a/en-US/Controlling_Access_to_Services.xml
+++ b/en-US/Controlling_Access_to_Services.xml
@@ -119,16 +119,13 @@ N 5</screen>
The default runlevel can be changed by modifying the <filename>/etc/inittab</filename> file, which contains a line near the end of the file similar to the following:
</para>
<screen>id:5:initdefault:</screen>
- <note>
- <title>Note</title>
- <para>
- In order to change this file, you must have superuser privileges. To obtain them, log in as root by typing the following command:
- </para>
- <screen>~]$ <command>su -</command>
+ <para>
+ In order to edit this file, you must have superuser privileges. To obtain them, log in as root by typing the following command:
+ </para>
+ <screen>~]$ <command>su -</command>
Password:</screen>
- </note>
<para>
- To change it to, lets say, runlevel 3, open the file in a text editor such as <application>vi</application> or <application>nano</application>:
+ Now open the file in a text editor such as <application>vi</application> or <application>nano</application>:
</para>
<screen>~]# <command>nano /etc/inittab</command></screen>
<para>Then change the number in this line to the desired value and exit the editor. Note that the change does not take effect until you reboot the system.</para>
@@ -136,54 +133,199 @@ Password:</screen>
<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>Using <application>Service Configuration</application> Utility</title>
+ <para>
+ The <application>Service Configuration</application> utility is a graphical application developed by Red Hat to configure which services are started at boot time, as well as to start, stop, and restart them from the menu.
+ </para>
+ <para>
+ To start the utility, select <menuchoice><guimenu>System</guimenu><guisubmenu>Administration</guisubmenu><guimenuitem>Services</guimenuitem></menuchoice> from the panel, or type the command <command>system-config-services</command> at a shell prompt (e.g., <emphasis>xterm</emphasis> or <emphasis>GNOME Terminal</emphasis>).
+ </para>
+ <figure id="fig-services-serviceconf">
<title>
- <application>Services Configuration Tool</application>
+ <application>Service Configuration </application> Utility
</title>
<mediaobject>
<imageobject>
- <imagedata
- fileref="images/serviceconf.png"
- format="PNG"
- scalefit="1"/>
+ <imagedata fileref="images/controlling-access-to-services-service_configuration.png" format="PNG" scalefit="1" />
</imageobject>
<textobject>
- <para>Configuring network services</para>
+ <para>Service Configuration Utility</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>
+ <para>
+ The utility displays the list of all available services (i.e., both the services from the <filename class="directory">/etc/rc.d/init.d/</filename> directory, and the services controlled by <application>xinetd</application>) along with their description and the current status. See <xref linkend="tab-services-serviceconf-states" /> for a complete list of used icons and an explanation of their meaning.
+ </para>
+ <table id="tab-services-serviceconf-states">
+ <title>Possible Service States</title>
+ <tgroup cols="2">
+ <colspec colname="icon" colnum="1" colwidth="10*" />
+ <colspec colname="description" colnum="2" colwidth="60*" />
+ <thead>
+ <row>
+ <entry>Icon</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/controlling-access-to-services-service_enabled.png" />
+ </imageobject>
+ <textobject>
+ <para>Green bullet</para>
+ </textobject>
+ </inlinemediaobject>
+ </entry>
+ <entry>
+ The service is enabled.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/controlling-access-to-services-service_disabled.png" />
+ </imageobject>
+ <textobject>
+ <para>Red bullet</para>
+ </textobject>
+ </inlinemediaobject>
+ </entry>
+ <entry>
+ The service is disabled.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/controlling-access-to-services-service_selected.png" />
+ </imageobject>
+ <textobject>
+ <para>Control panel</para>
+ </textobject>
+ </inlinemediaobject>
+ </entry>
+ <entry>
+ The service is enabled for selected runlevels only.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/controlling-access-to-services-service_running.png" />
+ </imageobject>
+ <textobject>
+ <para>Plugged plug</para>
+ </textobject>
+ </inlinemediaobject>
+ </entry>
+ <entry>
+ The service is running.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/controlling-access-to-services-service_stopped.png" />
+ </imageobject>
+ <textobject>
+ <para>Unplugged plug</para>
+ </textobject>
+ </inlinemediaobject>
+ </entry>
+ <entry>
+ The service is stopped.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/controlling-access-to-services-service_wrong.png" />
+ </imageobject>
+ <textobject>
+ <para>Exclamation mark</para>
+ </textobject>
+ </inlinemediaobject>
+ </entry>
+ <entry>
+ There is something wrong with the service.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="images/controlling-access-to-services-service_unknown.png" />
+ </imageobject>
+ <textobject>
+ <para>Question mark</para>
+ </textobject>
+ </inlinemediaobject>
+ </entry>
+ <entry>
+ The status of the service is unknown.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>
+ Unless you are already authenticated, you will be prompted to enter the superuser password the first time you make a change:
+ </para>
+ <figure id="fig-services-serviceconf-authentication">
+ <title>Authentication Query</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/controlling-access-to-services-authentication.png" format="PNG" scalefit="1" />
+ </imageobject>
+ <textobject>
+ <para>Authentication Query</para>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <section id="s3-services-serviceconf-enabling">
+ <title>Enabling the Service</title>
+ <para>
+ To enable a service, select it from the list and either click the <guilabel>Enable</guilabel> button on the toolbar, or choose <menuchoice><guimenu>Service</guimenu><guimenuitem>Enable</guimenuitem></menuchoice> from the main menu.
+ </para>
+ </section>
+ <section id="s3-services-serviceconf-disabling">
+ <title>Disabling the Service</title>
+ <para>
+ To disable the service, select it from the list and either click the <guilabel>Disable</guilabel> button on the toolbar, or choose <menuchoice><guimenu>Service</guimenu><guimenuitem>Disable</guimenuitem></menuchoice> from the main menu.
+ </para>
+ </section>
+ <section id="s3-services-serviceconf-running">
+ <title>Running the Service</title>
+ <para>
+ To run the service, select it from the list and either click the <guilabel>Start</guilabel> button on the toolbar, or choose <menuchoice><guimenu>Service</guimenu><guimenuitem>Start</guimenuitem></menuchoice> from the main menu.
+ </para>
+ </section>
+ <section id="s3-services-serviceconf-stopping">
+ <title>Stopping the Service</title>
+ <para>
+ To stop the service, select it from the list and either click the <guilabel>Stop</guilabel> button on the toolbar, or choose <menuchoice><guimenu>Service</guimenu><guimenuitem>Stop</guimenuitem></menuchoice> from the main menu.
+ </para>
+ </section>
+ <section id="s3-services-serviceconf-restarting">
+ <title>Restarting the Running Service</title>
+ <para>
+ To restart the running service, select it from the list and either click the <guilabel>Restart</guilabel> button on the toolbar, or choose <menuchoice><guimenu>Service</guimenu><guimenuitem>Restart</guimenuitem></menuchoice> from the main menu.
+ </para>
+ </section>
+ <section id="s3-services-serviceconf-selecting">
+ <title>Selecting the Runlevels</title>
+ <para>
+ To enable the service for certain runlevels only, select it from the list and either click the <guilabel>Customize</guilabel> button on the toolbar, or choose <menuchoice><guimenu>Service</guimenu><guisubmenu>Customize</guisubmenu></menuchoice> from the main menu. Then select the checkbox beside each runlevel in which you want the service to run.
+ </para>
+ </section>
</section>
<section id="s2-services-chkconfig">
<title>Using <command>chkconfig</command></title>
diff --git a/en-US/images/controlling-access-to-services-authentication.png b/en-US/images/controlling-access-to-services-authentication.png
new file mode 100644
index 0000000..2e84f56
Binary files /dev/null and b/en-US/images/controlling-access-to-services-authentication.png differ
diff --git a/en-US/images/controlling-access-to-services-service_configuration.png b/en-US/images/controlling-access-to-services-service_configuration.png
new file mode 100644
index 0000000..ea3a46b
Binary files /dev/null and b/en-US/images/controlling-access-to-services-service_configuration.png differ
diff --git a/en-US/images/controlling-access-to-services-service_disabled.png b/en-US/images/controlling-access-to-services-service_disabled.png
new file mode 100644
index 0000000..3dceb52
Binary files /dev/null and b/en-US/images/controlling-access-to-services-service_disabled.png differ
diff --git a/en-US/images/controlling-access-to-services-service_enabled.png b/en-US/images/controlling-access-to-services-service_enabled.png
new file mode 100644
index 0000000..dec0092
Binary files /dev/null and b/en-US/images/controlling-access-to-services-service_enabled.png differ
diff --git a/en-US/images/controlling-access-to-services-service_running.png b/en-US/images/controlling-access-to-services-service_running.png
new file mode 100644
index 0000000..c2d1ca0
Binary files /dev/null and b/en-US/images/controlling-access-to-services-service_running.png differ
diff --git a/en-US/images/controlling-access-to-services-service_selected.png b/en-US/images/controlling-access-to-services-service_selected.png
new file mode 100644
index 0000000..13d5262
Binary files /dev/null and b/en-US/images/controlling-access-to-services-service_selected.png differ
diff --git a/en-US/images/controlling-access-to-services-service_stopped.png b/en-US/images/controlling-access-to-services-service_stopped.png
new file mode 100644
index 0000000..bd9e1a8
Binary files /dev/null and b/en-US/images/controlling-access-to-services-service_stopped.png differ
diff --git a/en-US/images/controlling-access-to-services-service_unknown.png b/en-US/images/controlling-access-to-services-service_unknown.png
new file mode 100644
index 0000000..94dc930
Binary files /dev/null and b/en-US/images/controlling-access-to-services-service_unknown.png differ
diff --git a/en-US/images/controlling-access-to-services-service_wrong.png b/en-US/images/controlling-access-to-services-service_wrong.png
new file mode 100644
index 0000000..f59ef68
Binary files /dev/null and b/en-US/images/controlling-access-to-services-service_wrong.png differ
More information about the docs-commits
mailing list