June 2010 - docs-commits - Fedora Mailing-Lists

[deployment-guide/comm-rel: 19/26] Added other manual pages to the list.

by dsilas

commit 8fa64008bc23a3f6a0a3695275e3be799f9c6d5d Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Mon Jun 21 08:35:55 2010 +0200 Added other manual pages to the list. en-US/Controlling_Access_to_Services.xml | 16 ++++++++++++++++ 1 files changed, 16 insertions(+), 0 deletions(-) --- diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml index 5486374..fda4c90 100644 --- a/en-US/Controlling_Access_to_Services.xml +++ b/en-US/Controlling_Access_to_Services.xml @@ -541,6 +541,22 @@ rsync off</screen> </para> </listitem> </varlistentry> + <varlistentry> + <term><command>man ntsysv</command></term> + <listitem> + <para> + The manual page for the <command>ntsysv</command> utility containing the full documentation on its usage. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><command>man system-config-services</command></term> + <listitem> + <para> + The manual page for the <command>system-config-services</command> utility containing the full documentation on its usage. + </para> + </listitem> + </varlistentry> </variablelist> </section> <section id="s2-services-additional-resources-books">

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 18/26] Started updating the Console Access chapter.

by dsilas

commit 06545847cf9f24955e3fce4d0aebe1cff511b26b Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Mon Jun 21 08:30:40 2010 +0200 Started updating the Console Access chapter. en-US/Console_Access.xml | 30 +++++++++++++++++++++++------- 1 files changed, 23 insertions(+), 7 deletions(-) --- diff --git a/en-US/Console_Access.xml b/en-US/Console_Access.xml index 4fb9e3c..c779388 100644 --- a/en-US/Console_Access.xml +++ b/en-US/Console_Access.xml @@ -26,18 +26,33 @@ </para> <screen>~]$ <command>su -</command> Password: </screen> - <section - id="s1-access-console-ctrlaltdel"> - <title>Disabling Shutdown Via <keycombo><keycap>Ctrl</keycap> - <keycap>Alt</keycap> - <keycap>Del</keycap> - </keycombo> - </title> + <section id="s1-access-console-ctrlaltdel"> + <title>Disabling Shutdown Via <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo></title> + + <para> + By default, pressing <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap></keycombo> at the console causes system to reboot immediately. To disable this behavior, open the <filename>/etc/init/control-alt-delete.conf</filename> configuration file in a text editor such as <command>vi</command> or <command>nano</command>: + </para> + <screen>~]# <command>nano /etc/init/control-alt-delete.conf</command></screen> + <para> + Then find a line containing the following text and add a hash mark at its very beginning like this: + </para> + <screen>#start on control-alt-delete</screen> + <para> + Finally, save your changes, and exit the editor. The changes will take effect next time you reboot the computer. + </para> + <important> + <title>Important</title> + <para> + Being part of the <package>initscripts</package> package, <filename>/etc/init/control-alt-delete.conf</filename> will most likely be restored to its initial state the next time this package is upgraded. If that happens, repeat the process described in this section, or make a backup. + </para> + </important> + </section> <section id="s1-access-console-program">

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 17/26] Added index terms where appropriate.

by dsilas

commit 3944d8b27766c4d6227a0887679a87d692afad7f Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Thu Jun 17 14:37:37 2010 +0200 Added index terms where appropriate. en-US/Controlling_Access_to_Services.xml | 51 ++++++++++++++++++++++++++++++ 1 files changed, 51 insertions(+), 0 deletions(-) --- diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml index 93f5b4c..5486374 100644 --- a/en-US/Controlling_Access_to_Services.xml +++ b/en-US/Controlling_Access_to_Services.xml @@ -3,6 +3,9 @@ ]> <chapter id="ch-Controlling_Access_to_Services"> <title>Controlling Access to Services</title> + <indexterm> + <primary>services configuration</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> @@ -80,6 +83,18 @@ <para> To check in which runlevel you are operating, type the following: </para> + <indexterm significance="normal"> + <primary> + <command>runlevel</command> + </primary> + <see>services configuration</see> + </indexterm> + <indexterm> + <primary>services configuration</primary> + <secondary> + <command><command>runlevel</command></command> + </secondary> + </indexterm> <screen>~]$ <command>runlevel</command> N 5</screen> <para> @@ -107,6 +122,18 @@ Password:</screen> <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> + <indexterm significance="normal"> + <primary> + <command>system-config-services</command> + </primary> + <see>services configuration</see> + </indexterm> + <indexterm> + <primary>services configuration</primary> + <secondary> + <command>system-config-services</command> + </secondary> + </indexterm> <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> @@ -299,6 +326,18 @@ Password:</screen> </section> <section id="s2-services-ntsysv"> <title>Using the <application>ntsysv</application> Utility</title> + <indexterm significance="normal"> + <primary> + <command>ntsysv</command> + </primary> + <see>services configuration</see> + </indexterm> + <indexterm significance="normal"> + <primary>services configuration</primary> + <secondary> + <command>ntsysv</command> + </secondary> + </indexterm> <para> The <application>ntsysv</application> utility is a command line application with a simple text user interface to configure which services are to be started in selected runlevels. Note that in order to use the utility, you must obtain superuser privileges first: </para> @@ -381,6 +420,18 @@ Password: </screen> </section> <section id="s2-services-chkconfig"> <title>Using the <command>chkconfig</command> Utility</title> + <indexterm significance="normal"> + <primary> + <command>chkconfig</command> + </primary> + <see>services configuration</see> + </indexterm> + <indexterm> + <primary>services configuration</primary> + <secondary> + <command>chkconfig</command> + </secondary> + </indexterm> <para> The <application>chkconfig</application> utility is a command line application to configure which services are to be started in selected runlevels. It also allows you to list all available services along with their current setting. Note that with the exception of listing, you must have superuser privileges to use this command. To obtain them, log in as root by typing: </para>

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 16/26] Added a chapter outline to the introduction.

by dsilas

commit 6fbca30551d6a664e4fefbdaf2bc800229daa684 Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Thu Jun 17 11:02:35 2010 +0200 Added a chapter outline to the introduction. en-US/Controlling_Access_to_Services.xml | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) --- diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml index 968883e..93f5b4c 100644 --- a/en-US/Controlling_Access_to_Services.xml +++ b/en-US/Controlling_Access_to_Services.xml @@ -6,10 +6,13 @@ <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> + This chapter explains the concept of runlevels, and describes how to set the default one. It also covers the setup of the services to be run in each of them using three different utilities: the <application>Service Configuration</application> graphical application, the <application>ntsysv</application> text user interface, and the <application>chkconfig</application> command line tool. + </para> <important lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"> <title>Important</title> <para> - When you allow access for new services, always remember that both the firewall and <application>SELinux</application> 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 <citetitle pubwork="book">Security Guide: A Guide to Securing Red Hat Enterprise Linux</citetitle> for more information. + When you allow access for new services, always remember that both the firewall and <application>SELinux</application> 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 <citetitle pubwork="book">Security Guide: A Guide to Securing Red Hat Enterprise Linux</citetitle> (see <xref linkend="s1-services-additional-resources" />) for more information. </para> </important> <section id="s1-services-runlevels">

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 15/26] Updated the Additional Resources section.

by dsilas

commit 937a957f17e0b98afee802f960badb527e2a9f20 Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Wed Jun 16 17:04:43 2010 +0200 Updated the Additional Resources section. en-US/Controlling_Access_to_Services.xml | 45 ++++++++++++++++------------- 1 files changed, 25 insertions(+), 20 deletions(-) --- diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml index 55c868e..968883e 100644 --- a/en-US/Controlling_Access_to_Services.xml +++ b/en-US/Controlling_Access_to_Services.xml @@ -476,28 +476,33 @@ rsync off</screen> </section> <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="s2-services-additional-resources-installed"> <title>Installed Documentation</title> - <itemizedlist> - <listitem> - <para>The man pages for <command>ntsysv</command>, <command>chkconfig</command>, <command>xinetd</command>, and <filename>xinetd.conf</filename>.</para> - </listitem> - <listitem> - <para> - <command>man 5 hosts_access</command> — The man page for the format of host access control files (in section 5 of the man pages).</para> - </listitem> - </itemizedlist> + <variablelist> + <varlistentry> + <term><command>man chkconfig</command></term> + <listitem> + <para> + The manual page for the <command>chkconfig</command> utility containing the full documentation on its usage. + </para> + </listitem> + </varlistentry> + </variablelist> </section> - <section id="services-useful-websites"> - <title>Useful Websites</title> - <itemizedlist> - <listitem> - <para> - <ulink - url="http://www.xinetd.org">http://www.xinetd.org</ulink> — The <command>xinetd</command> webpage. It contains sample configuration files and a more detailed list of features.</para> - </listitem> - </itemizedlist> + <section id="s2-services-additional-resources-books"> + <title>Related Books</title> + <variablelist> + <varlistentry> + <term> + <citetitle pubwork="book">Security Guide</citetitle> — <ulink url="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6.0/html/Securi..." /> + </term> + <listitem> + <para> + A guide to securing Red Hat Enterprise Linux. It contains valuable information on how to set up the firewall, as well as the configuration of <application>SELinux</application>. + </para> + </listitem> + </varlistentry> + </variablelist> </section> </section> </chapter>

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 14/26] Simplified the chapter introduction.

by dsilas

commit e68c8b9238a80f6b8429394c1bf01b95fd31662c Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Wed Jun 16 16:34:38 2010 +0200 Simplified the chapter introduction. I have removed a lot of unnecessary information as I covered it in the rest of the chapter. en-US/Controlling_Access_to_Services.xml | 47 ++++------------------------- 1 files changed, 7 insertions(+), 40 deletions(-) --- diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml index a38edea..55c868e 100644 --- a/en-US/Controlling_Access_to_Services.xml +++ b/en-US/Controlling_Access_to_Services.xml @@ -3,47 +3,14 @@ ]> <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. 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> - <variablelist> - <varlistentry> - <term> - <application>Services Configuration Tool </application> - </term> - <listitem> - <para>This is a graphical application that displays a description of each service, displays whether each service is started at boot time (for runlevels 3, 4, and 5), and allows services to be started, stopped, and restarted.</para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <application>ntsysv</application> - </term> - <listitem> - <para>This is a text-based application that allows you to configure which services are started at boot time for each runlevel. Non-<command>xinetd</command> services can not be started, stopped, or restarted using this program.</para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <command>chkconfig</command> - </term> - <listitem> - <para>This is a command line utility that allows you to turn services on and off for the different runlevels. Non-<command>xinetd</command> services can not be started, stopped, or restarted using this utility.</para> - </listitem> - </varlistentry> - </variablelist> - <para>You may find that these tools are easier to use than the alternatives — editing the numerous symbolic links located in the directories below <filename>/etc/rc.d</filename> by hand or editing the <command>xinetd</command> configuration files in <filename>/etc/xinetd.d</filename>.</para> - <para>Another way to manage access to system services is by using <command>iptables</command> to configure an IP firewall. If you are a new Linux user, note that <command>iptables</command> may not be the best solution for you. Setting up <command>iptables</command> can be complicated, and is best tackled by experienced Linux system administrators.</para> - <para - lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"> - On the other hand, the benefit of using <command>iptables</command> is flexibility. For example, if you need a customized solution which provides certain hosts access to certain services, <command>iptables</command> can provide it for you. Refer to  and  for more information about <command>iptables</command>.</para> - <para - lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"> - Refer to  for more information.</para> - <important - lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"> + <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> + <important lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"> <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  for more information.</para> + <para> + When you allow access for new services, always remember that both the firewall and <application>SELinux</application> 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 <citetitle pubwork="book">Security Guide: A Guide to Securing Red Hat Enterprise Linux</citetitle> for more information. + </para> </important> <section id="s1-services-runlevels"> <title>Configuring the Default Runlevel</title>

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 13/26] Updated the ntsysv section.

by dsilas

commit 7fc1e1beb447420f3508e85c9cac902a438dc49a Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Wed Jun 16 16:01:00 2010 +0200 Updated the ntsysv section. en-US/Controlling_Access_to_Services.xml | 112 +++++++++++++++----- .../controlling-access-to-services-ntsysv.png | Bin 0 -> 110269 bytes en-US/images/ntsysv.png | Bin 15885 -> 0 bytes 3 files changed, 84 insertions(+), 28 deletions(-) --- diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml index 253a546..a38edea 100644 --- a/en-US/Controlling_Access_to_Services.xml +++ b/en-US/Controlling_Access_to_Services.xml @@ -142,14 +142,14 @@ Password:</screen> </para> <figure id="fig-services-serviceconf"> <title> - <application>Service Configuration </application> Utility + <application>The Service Configuration </application> Utility </title> <mediaobject> <imageobject> <imagedata fileref="images/controlling-access-to-services-service_configuration.png" format="PNG" scalefit="1" /> </imageobject> <textobject> - <para>Service Configuration Utility</para> + <para>The Service Configuration Utility</para> </textobject> </mediaobject> </figure> @@ -327,6 +327,88 @@ Password:</screen> </para> </section> </section> + <section id="s2-services-ntsysv"> + <title>Using the <application>ntsysv</application> Utility</title> + <para> + The <application>ntsysv</application> utility is a command line application with a simple text user interface to configure which services are to be started in selected runlevels. Note that in order to use the utility, you must obtain superuser privileges first: + </para> + <screen>~]$ <command>su -</command> +Password: </screen> + <para> + To start the utility, type the following command: + </para> + <screen>~]# <command>ntsysv</command></screen> + <figure float="0" id="fig-ntsysv"> + <title>The <application>ntsysv</application> utility</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/controlling-access-to-services-ntsysv.png" format="PNG"/> + </imageobject> + <textobject> + <para>The <application>ntsysv</application> utility</para> + </textobject> + </mediaobject> + </figure> + <para> + The utility displays the list of available services (i.e., the services from the <filename class="directory">/etc/rc.d/init.d/</filename> directory) along with their current status and a description obtainable by pressing <keycap>F1</keycap>. See <xref linkend="tab-services-ntsysv-states" /> for a list of used symbols and an explanation of their meaning. + </para> + <table id="tab-services-ntsysv-states"> + <title>Possible Service States</title> + <tgroup cols="2"> + <colspec colname="symbol" colnum="1" colwidth="10*" /> + <colspec colname="description" colnum="2" colwidth="60*" /> + <thead> + <row> + <entry>Symbol</entry> + <entry>Description</entry> + </row> + </thead> + <tbody> + <row> + <entry> + <guilabel>[*]</guilabel> + </entry> + <entry> + The service is enabled. + </entry> + </row> + <row> + <entry> + <guilabel>[ ]</guilabel> + </entry> + <entry> + The service is disabled. + </entry> + </row> + </tbody> + </tgroup> + </table> + <section id="s3-services-ntsysv-enabling"> + <title>Enabling the Service</title> + <para> + To enable a service, navigate through the list using the <keycap>Up</keycap> and <keycap>Down</keycap> arrows keys, and select it with the <keycap>Spacebar</keycap>. An asterisk (<guilabel>*</guilabel>) should appear in the brackets. Once you are done, use <keycap>Tab</keycap> to navigate to the <guibutton>Ok</guibutton> button, and confirm the changes by pressing <keycap>Enter</keycap>. + </para> + <para> + Please, keep in mind that <application>ntsysv</application> does not actually run the service. If you need to start the service immediately, use the <command>service <replaceable><service></replaceable> start</command> command. + </para> + </section> + <section id="s3-services-ntsysv-disabling"> + <title>Disabling the Service</title> + <para> + To disable a service, navigate through the list using the <keycap>Up</keycap> and <keycap>Down</keycap> arrows keys, and toggle its status with the <keycap>Spacebar</keycap>. An asterisk (<guilabel>*</guilabel>) in the brackets should disappear. Once you are done, use <keycap>Tab</keycap> to navigate to the <guibutton>Ok</guibutton> button, and confirm the changes by pressing <keycap>Enter</keycap>. + </para> + <para> + Please, keep in mind that <application>ntsysv</application> does not actually stop the service. If you need to stop the service immediately, use the <command>service <replaceable><service></replaceable> stop</command> command. + </para> + </section> + <section id="s3-services-ntsysv-selecting"> + <title>Selecting the Runlevels</title> + <para> + By default, the <application>ntsysv</application> utility affects the current runlevel only. To enable or disable services for other runlevels, run the command with the additional <option>--level</option> option followed by the string of numbers from 0 to 6 representing each runlevel you want to configure. For example, to configure runlevels 3 and 5, type: + </para> + <screen>~]# <command>ntsysv --level 35</command></screen> + </section> + </section> <section id="s2-services-chkconfig"> <title>Using the <command>chkconfig</command> Utility</title> <para> @@ -406,32 +488,6 @@ rsync off</screen> </para> </section> </section> - <section id="s2-services-ntsysv"> - <title>Using the <application>ntsysv</application> Utility</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> -  - <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> diff --git a/en-US/images/controlling-access-to-services-ntsysv.png b/en-US/images/controlling-access-to-services-ntsysv.png new file mode 100644 index 0000000..70bc146 Binary files /dev/null and b/en-US/images/controlling-access-to-services-ntsysv.png differ

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 12/26] Updated the chkconfig section.

by dsilas

commit c1c4bccad0703ed3ee9adbf46ef2b45219929806 Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Tue Jun 15 18:43:09 2010 +0200 Updated the chkconfig section. en-US/Controlling_Access_to_Services.xml | 95 ++++++++++++++++++++++++----- 1 files changed, 78 insertions(+), 17 deletions(-) --- diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml index 9950012..253a546 100644 --- a/en-US/Controlling_Access_to_Services.xml +++ b/en-US/Controlling_Access_to_Services.xml @@ -133,7 +133,7 @@ Password:</screen> <section id="s1-services-services"> <title>Configuring Running Services</title> <section id="s2-services-serviceconf"> - <title>Using <application>Service Configuration</application> Utility</title> + <title>Using the <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> @@ -328,25 +328,86 @@ Password:</screen> </section> </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> + <title>Using the <command>chkconfig</command> Utility</title> <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> + The <application>chkconfig</application> utility is a command line application to configure which services are to be started in selected runlevels. It also allows you to list all available services along with their current setting. Note that with the exception of listing, you must have superuser privileges to use this command. To obtain them, log in as root by typing: + </para> + <screen>~]$ <command>su -</command> +Password: </screen> + <section id="s3-services-chkconfig-listing"> + <title>Listing the Services</title> + <para> + To display a list of system services (i.e., the services from the <filename class="directory">/etc/rc.d/init.d/</filename> directpry), either type <command>chkconfig --list</command>, or use <command>chkconfig</command> with no additional arguments. You should be presented with an output similar to this: + </para> + <screen>~]# <command>chkconfig --list</command> +NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off +abrtd 0:off 1:off 2:off 3:on 4:off 5:on 6:off +acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off +anamon 0:off 1:off 2:off 3:off 4:off 5:off 6:off +atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off +auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off +avahi-daemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off +<emphasis>... several lines omitted ...</emphasis> +wpa_supplicant 0:off 1:off 2:off 3:off 4:off 5:off 6:off</screen> + <para> + As you can see, each line consists of the name of the service followed by its status (<emphasis>on</emphasis> or <emphasis>off</emphasis>) for each of the seven numbered runlevels. For example, in the listing above, <application>NetworkManager</application> is enabled for runlevel 2, 3, 4, and 5, while <application>abrtd</application> runs in runlevel 3 and 5. + </para> + <para> + To display the current settings for selected service only, use <command>chkconfig --list</command> followed by the name of the service: + </para> + <screen>~]# <command>chkconfig --list sshd</command> +sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off</screen> + <para> + You can also use <command>chkconfig --list <replaceable><service></replaceable></command> to display the status of a service that is managed by <application>xinetd</application>. In that case, the output will simply contain the information whether the service is enabled or disabled: + </para> + <screen>~]# <command>chkconfig --list rsync</command> +rsync off</screen> + </section> + <section id="s3-services-chkconfig-enabling"> + <title>Enabling the Service</title> + <para> + To enable the service for runlevels 2, 3, 4, and 5 at the same time, type <command>chkconfig <replaceable><service></replaceable> on</command>. For instance: + </para> + <screen>~]# <command>chkconfig httpd on</command></screen> + <para> + To enable the service for certain runlevels only, add the <option>--level</option> option followed by the string of numbers from 0 to 6 representing each runlevel in which you want the service to run. For example, to enable the <application>abrtd</application> for runlevels 3 and 5, type: + </para> + <screen>~]# <command>chkconfig abrtd on --level 35</command></screen> + <para> + The service will be started the next time you enter one of these runlevels. If you need to start the service immediately, use the <command>service <replaceable><service></replaceable> start</command> command. + </para> + <para> + To enable the service that is managed by <application>xinetd</application>, use <command>chkconfig <replaceable><service></replaceable> on</command> only, as the <option>--level</option> option is not allowed: + </para> + <screen>~]# <command>chkconfig rsync on</command></screen> + <para> + If the <application>xinetd</application> daemon is running, the service is immediately enabled without having to restart the daemon manually. + </para> + </section> + <section id="s3-services-chkconfig-disabling"> + <title>Disabling the Service</title> + <para> + To disable the service for runlevels 2, 3, 4, and 5 at the same time, type <command>chkconfig <replaceable><service></replaceable> off</command>. For instance: + </para> + <screen>~]# <command>chkconfig httpd off</command></screen> + <para> + To disable the service for certain runlevels only, add the <option>--level</option> option followed by the string of numbers from 0 to 6 representing each runlevel in which you want the service to run. For example, to disable the <application>abrtd</application> for runlevels 2 and 4, type: + </para> + <screen>~]# <command>chkconfig abrtd off --level 24</command></screen> + <para> + The service will be stopped the next time you enter one of these runlevels. If you need to stop the service immediately, use the <command>service <replaceable><service></replaceable> stop</command> command. + </para> + <para> + To disable the service that is managed by <application>xinetd</application>, use <command>chkconfig <replaceable><service></replaceable> off</command> only, as the <option>--level</option> option is not allowed: + </para> + <screen>~]# <command>chkconfig rsync off</command></screen> + <para> + If the <application>xinetd</application> daemon is running, the service is immediately disabled without having to restart the daemon manually. + </para> + </section> </section> <section id="s2-services-ntsysv"> - <title>Using <application>ntsysv</application></title> + <title>Using the <application>ntsysv</application> Utility</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>

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 11/26] Updated the Service Tool section.

by dsilas

commit 89e73646c654a2d27b5f5aa92aeb00349e7361b9 Author: Jaromir Hradilek <jhradile(a)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  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 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 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 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

14 years

1
0
0 / 0

[deployment-guide/comm-rel: 10/26] Updated the section about runlevels.

by dsilas

commit c20a7b91381ee448953cc9ac5bc1042b7c5974c6 Author: Jaromir Hradilek <jhradile(a)redhat.com> Date: Mon Jun 14 13:40:54 2010 +0200 Updated the section about runlevels. en-US/Controlling_Access_to_Services.xml | 38 +++++++++++++++++++++++------ 1 files changed, 30 insertions(+), 8 deletions(-) --- diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml index 14ad9c4..56439ef 100644 --- a/en-US/Controlling_Access_to_Services.xml +++ b/en-US/Controlling_Access_to_Services.xml @@ -47,8 +47,9 @@ </important> <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> + <para> + A <firstterm>runlevel</firstterm> is a state, or <firstterm>mode</firstterm>, defined by services that are meant to be run when this runlevel is selected. Seven numbered runlevels exist (indexed from <emphasis>0</emphasis>): + </para> <table id="table-services-runlevels"> <title>Runlevels in &MAJOROS;</title> <tgroup cols="2"> @@ -82,7 +83,7 @@ <row> <entry><option>3</option></entry> <entry> - Used to run in full multi-user mode with a command line user interface. + Used to run in a full multi-user mode with a command line user interface. </entry> </row> <row> @@ -94,7 +95,7 @@ <row> <entry><option>5</option></entry> <entry> - Used to run in full multi-user mode with a graphical user interface. + Used to run in a full multi-user mode with a graphical user interface. </entry> </row> <row> @@ -106,15 +107,36 @@ </tbody> </tgroup> </table> - <para>If you use a text login screen, you are operating in runlevel 3. If you use a graphical login screen, you are operating in runlevel 5.</para> - <para>The default runlevel can be changed by modifying the <filename>/etc/inittab</filename> file, which contains a line near the top of the file similar to the following:</para> + <para> + To check in which runlevel you are operating, type the following: + </para> + <screen>~]$ <command>runlevel</command> +N 5</screen> + <para> + The <command>runlevel</command> command displays previous and current runlevel. In this case it is number <emphasis>5</emphasis>, which means the system is running in a full multi-user mode with a graphical user interface. + </para> + <para> + 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> - <para>Change the number in this line to the desired runlevel. The change does not take effect until you reboot the system.</para> + <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> +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>: + </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> </section> <section id="s1-services-services"> <title>Configuring Running Services</title> <section id="s2-services-serviceconf"> - <title>Using <application>Service Configuration</application> tool</title> + <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  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

14 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits June 2010