[deployment-guide/comm-rel: 10/26] Updated the section about runlevels.
dsilas
dsilas at fedoraproject.org
Mon Jun 21 11:42:23 UTC 2010
commit c20a7b91381ee448953cc9ac5bc1042b7c5974c6
Author: Jaromir Hradilek <jhradile at 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 <!-- 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
More information about the docs-commits
mailing list