[deployment-guide] Updated the "Services and Daemons" chapter for Fedora 15.
Jaromir Hradilek
jhradile at fedoraproject.org
Mon May 23 21:36:32 UTC 2011
commit 837c4adb0ee382d8136143aa704aad7b5f132f86
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Mon May 23 23:19:46 2011 +0200
Updated the "Services and Daemons" chapter for Fedora 15.
en-US/Automating_System_Tasks.xml | 12 +-
en-US/DHCP_Servers.xml | 8 +-
en-US/DNS_Servers.xml | 5 +-
en-US/Deployment_Guide.xml | 2 +-
en-US/FTP.xml | 10 +-
en-US/Mail_Servers.xml | 6 +-
en-US/Network_Interfaces.xml | 16 +-
en-US/OpenLDAP.xml | 8 +-
en-US/OpenSSH.xml | 8 +-
en-US/Preface.xml | 2 +
en-US/Samba.xml | 4 +-
en-US/Services_and_Daemons.xml | 620 +++++++++----------------------------
en-US/The_Apache_HTTP_Server.xml | 20 +-
en-US/The_sysconfig_Directory.xml | 6 +-
14 files changed, 194 insertions(+), 533 deletions(-)
---
diff --git a/en-US/Automating_System_Tasks.xml b/en-US/Automating_System_Tasks.xml
index de41b4c..7b603f1 100644
--- a/en-US/Automating_System_Tasks.xml
+++ b/en-US/Automating_System_Tasks.xml
@@ -35,9 +35,9 @@
<screen><command>systemctl stop crond.service</command></screen>
<para>It is recommended that you start the service at boot time. To do so, use the following command as <systemitem class="username">root</systemitem>:</para>
<screen><command>systemctl enable crond.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment the following line as soon as the Services and Daemons chapter is updated.
- </para>Refer to <xref linkend="ch-Services_and_Daemons" /> for details on starting the cron service automatically at boot time.</para>
- -->
+ <para>
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ </para>
</section>
<section id="s2-configuring-anacron-jobs">
<title>Configuring Anacron Jobs</title>
@@ -390,9 +390,9 @@ HOME=/
<screen><command>systemctl stop atd.service</command></screen>
<para>It is recommended that you start the service at boot time. To do so, run the following command as <systemitem class="username">root</systemitem>:</para>
<screen><command>systemctl enable atd.service</command></screen>
- <!-- jhradilek: TBD F15: Uncomment the following line as soon as the Services and Daemons chapter is updated.
- <para>Refer to <xref linkend="ch-Services_and_Daemons" /> for details on starting the cron service automatically at boot time.</para>
- -->
+ <para>
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ </para>
</section>
</section>
<section id="s1-autotasks-additional-resources">
diff --git a/en-US/DHCP_Servers.xml b/en-US/DHCP_Servers.xml
index 88a6156..98091bd 100644
--- a/en-US/DHCP_Servers.xml
+++ b/en-US/DHCP_Servers.xml
@@ -242,9 +242,9 @@ subnet 192.168.1.0 netmask 255.255.255.0 {
<screen><command>systemctl stop dhcpd.service</command></screen>
<para>By default, the DHCP service does not start at boot time. To configure the daemon to start automatically at boot time, run:</para>
<screen><command>systemctl enable dhcpcd.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
- <para>For more information on how to configure sevices in &MAJOROSVER;, refer to <xref linkend="ch-Services_and_Daemons" />.</para>
- -->
+ <para>
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ </para>
<indexterm
significance="normal">
<primary>
@@ -363,8 +363,10 @@ ONBOOT=yes</programlisting>
</itemizedlist>
</listitem>
</itemizedlist>
+ <!-- jhradilek: TBD F15: Uncomment this as soon as the NetworkManager chapter is updated.
<para>If you prefer using a graphical interface, refer to <xref
linkend="ch-NetworkManager" /> for instructions on using the <application>Network Administration Tool</application> to configure a network interface to use DHCP.</para>
+ -->
<note>
<title>Advanced configurations</title>
<para>For advanced configurations of client DHCP options such as protocol timing, lease requirements and requests, dynamic DNS support, aliases, as well as a wide variety of values to override, prepend, or append to client-side configurations, refer to the <command>dhclient</command> and <command>dhclient.conf</command> man pages.</para>
diff --git a/en-US/DNS_Servers.xml b/en-US/DNS_Servers.xml
index 6af2fd4..e6f5c54 100644
--- a/en-US/DNS_Servers.xml
+++ b/en-US/DNS_Servers.xml
@@ -165,10 +165,7 @@
<see>BIND</see>
</indexterm>
<para>
- BIND consists of a set of DNS-related programs. It contains a monolithic nameserver called <systemitem class="service">named</systemitem>, an administration utility called <command>rndc</command>, and a debugging tool called <command>dig</command>.
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to run a service in &MAJOROS;.
- -->
+ BIND consists of a set of DNS-related programs. It contains a monolithic nameserver called <systemitem class="service">named</systemitem>, an administration utility called <command>rndc</command>, and a debugging tool called <command>dig</command>. Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
</section>
diff --git a/en-US/Deployment_Guide.xml b/en-US/Deployment_Guide.xml
index 81fc0b4..6f94af1 100644
--- a/en-US/Deployment_Guide.xml
+++ b/en-US/Deployment_Guide.xml
@@ -36,7 +36,7 @@
This part describes how to configure the network on &MAJOROS;.
</para>
</partintro>
- <xi:include href="NetworkManager.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- <xi:include href="NetworkManager.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include href="Network_Interfaces.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
<part id="part-Infrastructure_Services">
diff --git a/en-US/FTP.xml b/en-US/FTP.xml
index 526f78c..4ba1f45 100644
--- a/en-US/FTP.xml
+++ b/en-US/FTP.xml
@@ -260,9 +260,7 @@
<para>To conditionally restart the server, as <systemitem class="username">root</systemitem> type:</para>
<screen><command>systemctl condrestart vsftpd.service</command></screen>
<para>
- By default, the <command>vsftpd</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure the <command>vsftpd</command> service to start at boot time, use a service manager such as <command>systemctl</command><!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons chapter is updated.
- , <application>/usr/sbin/ntsysv</application>, or the <application>Services Configuration Tool</application> program. Refer to <xref
- linkend="ch-Services_and_Daemons" /> for more information regarding these tools-->.</para>
+ By default, the <command>vsftpd</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure the <command>vsftpd</command> service to start at boot time, use a service manager such as <command>systemctl</command>. Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.</para>
<section
id="s3-ftp-vsftpd-start-multi">
<title>Starting Multiple Copies of <command>vsftpd</command>
@@ -282,7 +280,11 @@
<secondary>multihome configuration</secondary>
</indexterm>
<para>Sometimes one computer is used to serve multiple <systemitem class="protocol">FTP</systemitem> domains. This is a technique called <firstterm>multihoming</firstterm>. One way to multihome using <command>vsftpd</command> is by running multiple copies of the daemon, each with its own configuration file.</para>
- <para>To do this, first assign all relevant <systemitem class="protocol">IP</systemitem> addresses to network devices or alias network devices on the system. Refer to <xref linkend="ch-NetworkManager" /> for more information about configuring network devices and device aliases. Additional information about network configuration scripts can be found in <xref linkend="ch-Network_Interfaces"/>.</para>
+ <para>To do this, first assign all relevant <systemitem class="protocol">IP</systemitem> addresses to network devices or alias network devices on the system.
+ <!-- jhradilek: TBD F15: Uncomment this as soon as the NetworkManager chapter is updated.
+ Refer to <xref linkend="ch-NetworkManager" /> for more information about configuring network devices and device aliases.
+ -->
+ Additional information about network configuration scripts can be found in <xref linkend="ch-Network_Interfaces"/>.</para>
<para>Next, the DNS server for the <systemitem class="protocol">FTP</systemitem> domains must be configured to reference the correct machine. For information about BIND and its configuration files, refer to <xref linkend="s1-BIND" />.</para>
<para>
If there is more configuration files present in the <filename>/etc/vsftpd</filename> directory, calling <command>systemctl start vsftpd.service</command> results in the <filename>/etc/rc.d/init.d/vsftpd</filename> initscript starting the same number of processes as the number of configuration files. Each configuration file must have a unique name in the <filename>/etc/vsftpd/</filename> directory and must be readable and writable only by <systemitem class="username">root</systemitem>.
diff --git a/en-US/Mail_Servers.xml b/en-US/Mail_Servers.xml
index 9665ef8..32c8317 100644
--- a/en-US/Mail_Servers.xml
+++ b/en-US/Mail_Servers.xml
@@ -1296,9 +1296,9 @@ poll mail.domain2.com
<screen><command>systemctl start spamassassin.service</command></screen>
<para>To start the SpamAssassin daemon when the system is booted, run:</para>
<screen><command>systemctl enable spamassassin.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
- <para>To start the SpamAssassin daemon when the system is booted, use an initscript utility, such as the <application>Services Configuration Tool</application> (<command>system-config-services</command>), to turn on the <computeroutput>spamassassin</computeroutput> service. Refer to <xref linkend="ch-Services_and_Daemons" /> for more information about starting and stopping services.</para>
- -->
+ <para>
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ </para>
<para>To configure Procmail to use the SpamAssassin client application instead of the Perl script, place the following line near the top of the <filename>~/.procmailrc</filename> file. For a system-wide configuration, place it in <filename>/etc/procmailrc</filename>:</para>
<programlisting>INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc</programlisting>
</section>
diff --git a/en-US/Network_Interfaces.xml b/en-US/Network_Interfaces.xml
index c3ae964..94577a5 100644
--- a/en-US/Network_Interfaces.xml
+++ b/en-US/Network_Interfaces.xml
@@ -112,10 +112,12 @@
<title>Warning</title>
<para>The <filename>/etc/sysconfig/networking/</filename> directory is used by the <application>Network Administration Tool</application> (<command>system-config-network</command>) and its contents should <emphasis
role="bold">not</emphasis> be edited manually. <!-- RHEL5: ddomingo at redhat.com: string removed as per Harald Hoyer <string> In addition, any use of the <application>Network Administration Tool</application> (even launching the application) will override any directives previously set in <filename>/etc/sysconfig/network-scripts</filename>.</string> -->Using only one method for network configuration is strongly encouraged, due to the risk of configuration deletion.</para>
+ <!-- jhradilek: TBD F15: Uncomment this as soon as the NetworkManager chapter is updated.
<para>
For more information about configuring network interfaces using the <application>Network Administration Tool</application>, refer to <xref
linkend="ch-NetworkManager" />.
</para>
+ -->
</warning>
</section>
<section
@@ -161,8 +163,11 @@ USERCTL=no</programlisting>
BOOTPROTO=dhcp
ONBOOT=yes</programlisting>
<para>
- The <application>Network Administration Tool</application> (<command>system-config-network</command>) is an easy way to make changes to the various network interface configuration files (refer to <xref
- linkend="ch-NetworkManager" /> for detailed instructions on using this tool).</para>
+ The <application>Network Administration Tool</application> (<command>system-config-network</command>) is an easy way to make changes to the various network interface configuration files.
+ <!-- jhradilek: TBD F15: Uncomment this as soon as the NetworkManager chapter is updated.
+ (refer to <xref linkend="ch-NetworkManager" /> for detailed instructions on using this tool).
+ -->
+ </para>
<para>However, it is also possible to manually edit the configuration files for a given network interface.</para>
<para>Below is a listing of the configurable parameters in an Ethernet interface configuration file:</para>
<!-- RHEL5: added BONDING_OPTS as per BZ#221423 -->
@@ -520,8 +525,11 @@ BOOTPROTO=dhcp</programlisting>
<programlisting>USERCTL=yes</programlisting>
<para>This way a user can bring up the <filename>eth0</filename> interface using the <command>/sbin/ifup eth0-user</command> command because the configuration options from <filename>ifcfg-eth0</filename> and <filename>ifcfg-eth0-user</filename> are combined. While this is a very basic example, this method can be used with a variety of options and interfaces.</para>
<para>
- The easiest way to create alias and clone interface configuration files is to use the graphical <application>Network Administration Tool</application>. For more information on using this tool, refer to <xref
- linkend="ch-NetworkManager" />.</para>
+ The easiest way to create alias and clone interface configuration files is to use the graphical <application>Network Administration Tool</application>.
+ <!-- jhradilek: TBD F15: Uncomment this as soon as the NetworkManager chapter is updated.
+ For more information on using this tool, refer to <xref linkend="ch-NetworkManager" />.
+ -->
+ </para>
</section>
<section
id="s2-networkscripts-interfaces-ppp0">
diff --git a/en-US/OpenLDAP.xml b/en-US/OpenLDAP.xml
index 8e1cbf8..4013487 100644
--- a/en-US/OpenLDAP.xml
+++ b/en-US/OpenLDAP.xml
@@ -1091,11 +1091,9 @@ Re-enter new password:
If you want the service to start automatically at the boot time, use the following command:
</para>
<screen><command>systemctl enable slapd.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
<para>
- Note that you can also use the <application>Service Configuration</application> utility as described in <xref linkend="s3-services-serviceconf-enabling" />.
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
- -->
</section>
<section id="s3-ldap-running-stopping">
<title>Stopping the Service</title>
@@ -1111,11 +1109,9 @@ Re-enter new password:
To prevent the service from starting automatically at the boot time, type:
</para>
<screen><command>systemctl disable slapd.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
<para>
- Alternatively, you can use the <application>Service Configuration</application> utility as described in <xref linkend="s3-services-serviceconf-disabling" />.
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
- -->
</section>
<section id="s3-ldap-running-restarting">
<title>Restarting the Service</title>
diff --git a/en-US/OpenSSH.xml b/en-US/OpenSSH.xml
index 2a329ca..3184132 100644
--- a/en-US/OpenSSH.xml
+++ b/en-US/OpenSSH.xml
@@ -504,11 +504,9 @@
If you want the daemon to start automatically at the boot time, type:
</para>
<screen><command>systemctl enable sshd.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
<para>
- This will enable the service for all runlevels. For more configuration options, refer to <xref linkend="ch-Services_and_Daemons" /> for the detailed information on how to manage services.
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
- -->
<para>
Note that if you reinstall the system, a new set of identification keys will be created. As a result, clients who had connected to the system with any of the OpenSSH tools before the reinstall will see the following message:
</para>
@@ -549,11 +547,9 @@ It is also possible that the RSA host key has just been changed.</screen>
<command>systemctl disable rsh.service</command>
<command>systemctl disable rlogin.service</command>
<command>systemctl disable vsftpd.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
<para>
- For more information on runlevels and configuring services in general, refer to <xref linkend="ch-Services_and_Daemons" />.
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
- -->
</section>
<section id="s2-ssh-configuration-keypairs">
<title>Using a Key-Based Authentication</title>
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index 27436a6..1fa11a2 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -85,9 +85,11 @@
<para>
This part describes how to configure the network on &MAJOROS;.
</para>
+ <!-- jhradilek: TBD F15: Uncomment this as soon as the NetworkManager chapter is updated.
<para>
<xref linkend="ch-NetworkManager" /> focuses on <application>NetworkManager</application>, a dynamic network control and configuration system that attempts to keep network devices and connections up and active when they are available. Read this chapter for information how to run the <systemitem class="service">NetworkManager</systemitem> daemon, and how to interact with it using the corresponding applet for the notification area.
</para>
+ -->
<para>
<xref linkend="ch-Network_Interfaces" /> explores various interface configuration files, interface control scripts, and network function files located in the <filename class="directory">/etc/sysconfig/network-scripts/</filename> directory. Read this chapter for information how to use these files to configure network interfaces.
</para>
diff --git a/en-US/Samba.xml b/en-US/Samba.xml
index 88e9d56..1e2cc24 100644
--- a/en-US/Samba.xml
+++ b/en-US/Samba.xml
@@ -622,9 +622,7 @@ create mask = 0765</programlisting>
<screen><command>systemctl condrestart smb.service</command></screen>
<para>A manual reload of the <filename>/etc/samba/smb.conf</filename> file can be useful in case of a failed automatic reload by the <command>smb</command> service. To ensure that the Samba server configuration file is reloaded without restarting the service, type the following command, as <systemitem class="username">root</systemitem>:</para>
<screen><command>systemctl reload smb.service</command></screen>
- <para>By default, the <command>smb</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure Samba to start at boot time, use a service manager such as <command>systemctl</command><!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons chapter is updated.
- , or the <application>Services Configuration Tool</application> program. Refer to <xref
- linkend="ch-Services_and_Daemons" /> for more information regarding these tools -->.</para>
+ <para>By default, the <command>smb</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure Samba to start at boot time, use a service manager such as <command>systemctl</command>. Refer to <xref linkend="ch-Services_and_Daemons" /> for more information regarding this tool.</para>
</section>
<!-- RHEL5: ddomingo at redhat.com: config guide used to be here, moved to before "Starting & Stopping" -->
<section
diff --git a/en-US/Services_and_Daemons.xml b/en-US/Services_and_Daemons.xml
index c141faa..83372be 100644
--- a/en-US/Services_and_Daemons.xml
+++ b/en-US/Services_and_Daemons.xml
@@ -7,10 +7,10 @@
<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.
+ 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, <systemitem class="service">httpd</systemitem> 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 these runlevels, and provides information on how to start, stop, and restart the services on the command line using the <application>service</application> command.
+ This chapter covers the configuration of the services to be run when a system is started, and provides information on how to start, stop, and restart the services on the command line using the <application>systemctl</application> utility.
</para>
<important>
<title>Keep the system secure</title>
@@ -18,6 +18,7 @@
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 the &MAJOROS; <citetitle pubwork="book">Security Guide</citetitle> (see <xref linkend="s1-services-additional-resources" />) for more information.
</para>
</important>
+ <!-- jhradile: TBD F15: Write the documentation on systemd's targets.
<section id="s1-services-runlevels">
<title>Configuring the Default Runlevel</title>
<para>
@@ -115,548 +116,213 @@ Password:</screen>
<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-configuring">
- <title>Configuring the Services</title>
+ <title>Configuring Services</title>
+ <indexterm significance="normal">
+ <primary>
+ <command>systemctl</command>
+ </primary>
+ <see>services configuration</see>
+ </indexterm>
+ <indexterm>
+ <primary>services configuration</primary>
+ <secondary>
+ <command>systemctl</command>
+ </secondary>
+ </indexterm>
<para>
- To allow you to configure which services are started at boot time, &MAJOROS; is shipped with the following utilities: the <application>Service Configuration</application> graphical application, the <application>ntsysv</application> text user interface, and the <application>chkconfig</application> command line tool.
+ To allow you to configure which services are started at boot time, &MAJOROS; is shipped with the <application>systemctl</application> command line tool.
</para>
- <important>
- <title>Enabling the irqbalance service</title>
+ <note>
+ <title>Do not use the ntsysv and chkconfig utilities</title>
<para>
- To ensure optimal performance on POWER architecture, it is recommended that the <systemitem class="service">irqbalance</systemitem> service is enabled. In most cases, this service is installed and configured to run during the &MAJOROSVER; installation. To verify that <systemitem class="service">irqbalance</systemitem> is running, as <systemitem class="username">root</systemitem>, type the following at a shell prompt:
+ Although it is still possible to use the <application>ntsysv</application> and <application>chkconfig</application> utilities to manage services that have init scripts installed in the <filename class="directory">/etc/rc.d/init.d/</filename> directory, it is advised that you use the <application>systemctl</application> utility.
</para>
- <screen>~]# <command>service irqbalance status</command>
-irqbalance (pid 1234) is running...</screen>
+ </note>
+ <important>
+ <title>Enabling the irqbalance service</title>
<para>
- For information on how to enable and run a service using a graphical user interface, refer to <xref linkend="s2-services-serviceconf" />. For instructions on how to perform these task on the command line, see <xref linkend="s2-services-chkconfig" /> and <xref linkend="s1-services-running" /> respectively.
+ To ensure optimal performance on POWER architecture, it is recommended that the <systemitem class="service">irqbalance</systemitem> service is enabled. In most cases, this service is installed and configured to run during the &MAJOROSVER; installation. To verify that <systemitem class="service">irqbalance</systemitem> is running, type the following at a shell prompt:
</para>
+ <screen><command>systemctl status irqbalance.service</command></screen>
</important>
- <section id="s2-services-serviceconf">
- <title>Using the Service Configuration Utility</title>
+ <section id="s3-services-configuration-enabling">
+ <title>Enabling the Service</title>
<para>
- The <application>Service Configuration</application> utility is a graphical application developed by Red Hat to configure which services are started in a particular runlevel, as well as to start, stop, and restart them from the menu.
+ To configure a service to be automatically started at boot time, use the <command>systemctl</command> command in the following form:
</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>
+ <screen><command>systemctl</command> <option>enable</option> <option><replaceable>service_name</replaceable>.service</option></screen>
<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>).
+ For example, to enable the <systemitem class="service">httpd</systemitem> service, type the following at a shell prompt as <systemitem class="username">root</systemitem>:
</para>
- <figure id="fig-services-serviceconf">
- <title>The Service Configuration utility</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/controlling-access-to-services-service_configuration.png" format="PNG" scalefit="1" />
- </imageobject>
- <textobject>
- <para>The Service Configuration Utility</para>
- </textobject>
- </mediaobject>
- </figure>
+ <screen>~]# <command>systemctl enable httpd.service</command></screen>
<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.
+ The service will be started the next time you boot the system. If you need to start the service immediately, use the <command>systemctl</command> command as described in <xref linkend="s3-services-running-running" />.
</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. Note that this option is not available for services controlled by <application>xinetd</application>, as they are started by it on demand.
- </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. Note that this option is not available for services controlled by <application>xinetd</application>, as they are stopped by it when their job is finished.
- </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. Note that this option is not available for services controlled by <application>xinetd</application>, as they are started and stopped by it automatically.
- </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. Note that this option is not available for services controlled by <application>xinetd</application>.
- </para>
- </section>
</section>
- <section id="s2-services-ntsysv">
- <title>Using the ntsysv 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>
- <screen>~]$ <command>su -</command>
-Password: </screen>
+ <section id="s3-services-configuration-disabling">
+ <title>Disabling the Service</title>
<para>
- To start the utility, type the following command:
+ To disable starting a service at boot time, use the <command>systemctl</command> command in the following form:
</para>
- <screen>~]# <command>ntsysv</command></screen>
- <figure float="0" id="fig-ntsysv">
- <title>The ntsysv 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>
+ <screen><command>systemctl</command> <option>disable</option> <option><replaceable>service_name</replaceable>.service</option></screen>
<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.
+ For example, to disable the <systemitem class="service">httpd</systemitem> service, type the following at a shell prompt as <systemitem class="username">root</systemitem>:
</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</command> command as described in <xref linkend="s3-services-running-running" />.
- </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</command> command as described in <xref linkend="s3-services-running-stopping" />.
- </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 chkconfig 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>
+ <screen>~]# <command>systemctl disable httpd.service</command></screen>
<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:
+ The next time you boot the system, the service will <emphasis>not</emphasis> be started. If you need to stop the service immediately, use the <command>systemctl</command> command as described in <xref linkend="s3-services-running-stopping" />.
</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., both the services from the <filename class="directory">/etc/rc.d/init.d/</filename> directory, and the services controlled by <application>xinetd</application>), 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>
- <example id="ex-services-chkconfig-listing-all">
- <title>Listing the services</title>
- <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
-
-xinetd based services:
- chargen-dgram: off
- chargen-stream: off
- cvs: off
- daytime-dgram: off
- daytime-stream: off
- discard-dgram: off
-<emphasis>... several lines omitted ...</emphasis>
- time-stream: off</screen>
- </example>
- <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. The <application>xinetd</application> based services are listed at the end, being either <emphasis>on</emphasis>, or <emphasis>off</emphasis>.
- </para>
- <para>
- To display the current settings for selected service only, use <command>chkconfig --list</command> followed by the name of the service:
- </para>
- <example id="ex-services-chkconfig-listing-single">
- <title>Listing a single service</title>
- <screen>~]# <command>chkconfig --list sshd</command>
-sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off</screen>
- </example>
- <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>
- <example id="ex-services-chkconfig-listing-xinetd">
- <title>Listing a service that is managed by xinetd</title>
- <screen>~]# <command>chkconfig --list rsync</command>
-rsync off</screen>
- </example>
- </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</command> command as described in <xref linkend="s3-services-running-running" />.
- </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 do <emphasis>not</emphasis> 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</command> command as described in <xref linkend="s3-services-running-stopping" />.
- </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>
<section id="s1-services-running">
- <title>Running the Services</title>
+ <title>Running Services</title>
<indexterm significance="normal">
<primary>
- <command>service</command>
+ <command>systemctl</command>
</primary>
<see>services configuration</see>
</indexterm>
<indexterm>
<primary>services configuration</primary>
<secondary>
- <command>service</command>
+ <command>ssystemctl</command>
</secondary>
</indexterm>
<para>
- The <application>service</application> utility enables you to start, stop, or restart the services from the <filename class="directory">/etc/init.d/</filename> directory. To use it, make sure you have superuser privileges:
+ The <application>systemctl</application> utility also allows you to determine the status of a particular service, as well as to start, stop, or restart a service.
</para>
- <screen>~]$ <command>su -</command>
-Password: </screen>
<note>
- <title>Use the Service Configuration utility</title>
+ <title>Do not use the service utility</title>
<para>
- If you are running a graphical user interface, you can also use the <application>Service Configuration</application> utility. See <xref linkend="s2-services-serviceconf" /> for more information.
+ Although it is still possible to use the <application>service</application> utility to manage services that have init scripts installed in the <filename class="directory">/etc/rc.d/init.d/</filename> directory, it is advised that you use the <application>systemctl</application> utility.
</para>
</note>
<section id="s3-services-running-checking">
<title>Checking the Service Status</title>
<para>
- To check the current status of the service, type <command>service <replaceable>service_name</replaceable> status</command>. For example:
+ To determine the status of a service, use the <command>systemctl</command> command in the following form:
+ </para>
+ <screen><command>systemctl</command> <option>status</option> <option><replaceable>service_name</replaceable>.service</option></screen>
+ <para>
+ For example, to determine the status of the <systemitem class="service">httpd</systemitem> service, type the following at a shell prompt:
+ </para>
+ <screen>~]$ <command>systemctl status httpd.service</command>
+httpd.service - LSB: start and stop Apache HTTP Server
+ Loaded: loaded (/etc/rc.d/init.d/httpd)
+ Active: active (running) since Mon, 23 May 2011 21:38:57 +0200; 27s ago
+ Process: 2997 ExecStart=/etc/rc.d/init.d/httpd start (code=exited, status=0/SUCCESS)
+ Main PID: 3002 (httpd)
+ CGroup: name=systemd:/system/httpd.service
+ ├ 3002 /usr/sbin/httpd
+ ├ 3004 /usr/sbin/httpd
+ ├ 3005 /usr/sbin/httpd
+ ├ 3006 /usr/sbin/httpd
+ ├ 3007 /usr/sbin/httpd
+ ├ 3008 /usr/sbin/httpd
+ ├ 3009 /usr/sbin/httpd
+ ├ 3010 /usr/sbin/httpd
+ └ 3011 /usr/sbin/httpd</screen>
+ <para>
+ The above command provides a detailed information on the service status. If you only need to verify that a service is running, use the <command>systemctl</command> command in the following form instead:
+ </para>
+ <screen><command>systemctl</command> <option>is-active</option> <option><replaceable>service_name</replaceable>.service</option></screen>
+ <para>
+ For example:
+ </para>
+ <screen>~]$ <command>systemctl is-active httpd.service</command>
+active</screen>
+ <para>
+ To display a list of all active system services, type:
+ </para>
+ <screen>~]$ <command>systemctl list-units --type=service</command>
+UNIT LOAD ACTIVE SUB JOB DESCRIPTION
+abrt-ccpp.service loaded active exited LSB: Installs coredump handler which saves segfault data
+abrt-oops.service loaded active running LSB: Watches system log for oops messages, creates ABRT dump directories for each oops
+abrtd.service loaded active running ABRT Automated Bug Reporting Tool
+accounts-daemon.service loaded active running Accounts Service
+atd.service loaded active running Job spooling tools
+<lineannotation>[output truncated]</lineannotation></screen>
+ <para>
+ As you can see, each line consists of the following columns:
</para>
- <example id="ex-services-running-checking-single">
- <title>Checking the status of httpd</title>
- <screen>~]# <command>service httpd status</command>
-httpd (pid 7474) is running...</screen>
- </example>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <computeroutput>UNIT</computeroutput> — Provides information whether the <systemitem class="service">systemd</systemitem> unit was properly loaded.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <computeroutput>ACTIVE</computeroutput> — Provides a high-level unit activation state.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <computeroutput>SUB</computeroutput> — Provides a low-level unit activation state.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <computeroutput>JOB</computeroutput> — Displays a pending job for a unit.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <computeroutput>DESCRIPTION</computeroutput> — Provides a brief description of the service.
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
- You can also display the status of all available services at once using the <option>--status-all</option> option:
+ In the example above, the <systemitem class="service">abrtd</systemitem> service is loaded, active, and running, and it does not have any pending jobs.
</para>
- <example id="ex-services-running-checking-all">
- <title>Checking the status of all services</title>
- <screen>~]# <command>service --status-all</command>
-abrt (pid 1492) is running...
-acpid (pid 1305) is running...
-atd (pid 1540) is running...
-auditd (pid 1103) is running...
-automount (pid 1315) is running...
-Avahi daemon is running
-cpuspeed is stopped
-<emphasis>... several lines omitted ...</emphasis>
-wpa_supplicant (pid 1227) is running...</screen>
- </example>
</section>
<section id="s3-services-running-running">
<title>Running the Service</title>
<para>
- To run the service, type <command>service <replaceable>service_name</replaceable> start</command>. For example:
+ To run a service, use the <command>systemctl</command> command in the following form:
</para>
- <screen>~]# <command>service httpd start</command>
-Starting httpd: [ OK ]</screen>
+ <screen><command>systemctl</command> <option>start</option> <option><replaceable>service_name</replaceable>.service</option></screen>
+ <para>
+ For example, to start the <systemitem class="service">httpd</systemitem> service, type the following at a shell prompt as <systemitem class="username">root</systemitem>:
+ </para>
+ <screen>~]# <command>systemctl start httpd.service</command></screen>
</section>
<section id="s3-services-running-stopping">
<title>Stopping the Service</title>
<para>
- To stop the service, type <command>service <replaceable>service_name</replaceable> stop</command>. For example:
+ To stop a service, use the <command>systemctl</command> command in the following form:
+ </para>
+ <screen><command>systemctl</command> <option>stop</option> <option><replaceable>service_name</replaceable>.service</option></screen>
+ <para>
+ For example, to stop the <systemitem class="service">httpd</systemitem> service, type the following at a shell prompt as <systemitem class="username">root</systemitem>:
</para>
- <screen>~]# <command>service httpd stop</command>
-Stopping httpd: [ OK ]</screen>
+ <screen>~]# <command>systemctl stop httpd.service</command></screen>
</section>
<section id="s3-services-running-restarting">
<title>Restarting the Service</title>
<para>
- To restart the service, type <command>service <replaceable>service_name</replaceable> restart</command>. For example:
+ To restart a service, use the <command>systemctl</command> command in the following form:
</para>
- <screen>~]# <command>service httpd restart</command>
-Stopping httpd: [ OK ]
-Starting httpd: [ OK ]</screen>
+ <screen><command>systemctl</command> <option>restart</option> <option><replaceable>service_name</replaceable>.service</option></screen>
+ <para>
+ For example, to restart the <systemitem class="service">httpd</systemitem> service, type the following at a shell prompt as <systemitem class="username">root</systemitem>:
+ </para>
+ <screen>~]# <command>systemctl restart httpd.service</command></screen>
</section>
</section>
<section id="s1-services-additional-resources">
<title>Additional Resources</title>
<section id="s2-services-additional-resources-installed">
<title>Installed Documentation</title>
- <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>
- <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 service</command></term>
- <listitem>
- <para>
- The manual page for the <command>service</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>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>systemctl</literal>(1) — The manual page for the <application>systemctl</application> utility.
+ </para>
+ </listitem>
+ </itemizedlist>
</section>
<section id="s2-services-additional-resources-books">
<title>Related Books</title>
diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_Server.xml
index 984562f..d64c8e9 100644
--- a/en-US/The_Apache_HTTP_Server.xml
+++ b/en-US/The_Apache_HTTP_Server.xml
@@ -167,11 +167,9 @@
If you want the service to start automatically at the boot time, use the following command:
</para>
<screen><command>systemctl enable httpd.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
<para>
- This will enable the service for runlevel 2, 3, 4, and 5. Alternatively, you can use the <application>Service Configuration</application> utility as described in <xref linkend="s3-services-serviceconf-enabling" />.
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
- -->
<note>
<title>Using the secure server</title>
<para>
@@ -194,7 +192,7 @@
</para>
<screen><command>systemctl disable httpd.service</command></screen>
<para>
- This will disable the service for all runlevels. Alternatively, you can use the <application>Service Configuration</application> utility as described in <xref linkend="s3-services-serviceconf-disabling" />.
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
<section id="s3-apache-running-restarting">
@@ -225,23 +223,19 @@
This will cause the running <systemitem class="service">httpd</systemitem> service to reload the configuration file. Note that any requests being currently processed will be interrupted, which may cause a client browser to display an error message or render a partial page.
</para>
</listitem>
- <!-- jhradile: TBD F15: Is there a way to perform a graceful restart with systemctl?
<listitem>
<para>
- To reload the configuration without affecting active requests, type:
+ To reload the configuration without affecting active requests, run the following command as <systemitem class="username">root</systemitem>:
</para>
- <screen>~]# <command>service httpd graceful</command></screen>
+ <screen><command>service httpd graceful</command></screen>
<para>
This will cause the running <systemitem class="service">httpd</systemitem> service to reload the configuration file. Note that any requests being currently processed will use the old configuration.
</para>
</listitem>
- -->
</orderedlist>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
<para>
- Alternatively, you can use the <application>Service Configuration</application> utility as described in <xref linkend="s3-services-serviceconf-restarting" />.
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
- -->
</section>
<section id="s3-apache-running-status">
<title>Checking the Service Status</title>
@@ -253,11 +247,9 @@
To check whether the service is running, type the following at a shell prompt:
</para>
<screen><command>systemctl is-active httpd.service</command></screen>
- <!-- jhradile: TBD F15: Uncomment this as soon as the Services and Daemons section is updated.
<para>
- Alternatively, you can use the <application>Service Configuration</application> utility as described in <xref linkend="s2-services-serviceconf" />.
+ Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
- -->
</section>
</section>
<section id="s2-apache-editing">
diff --git a/en-US/The_sysconfig_Directory.xml b/en-US/The_sysconfig_Directory.xml
index 6f91832..7a5ff2a 100644
--- a/en-US/The_sysconfig_Directory.xml
+++ b/en-US/The_sysconfig_Directory.xml
@@ -2086,8 +2086,10 @@
<secondary>
<filename>/etc/sysconfig/networking/</filename> directory</secondary>
</indexterm>
- This directory is used by the <application>Network Administration Tool</application> (<command>system-config-network</command>), and its contents should not be edited manually. For more information about configuring network interfaces using the <application>Network Administration Tool</application>, refer to <xref
- linkend="ch-NetworkManager" />.
+ This directory is used by the <application>Network Administration Tool</application> (<command>system-config-network</command>), and its contents should not be edited manually.
+ <!-- jhradilek: TBD F15: Uncomment this as soon as the NetworkManager chapter is updated.
+ For more information about configuring network interfaces using the <application>Network Administration Tool</application>, refer to <xref linkend="ch-NetworkManager" />.
+ -->
</para>
</listitem>
</varlistentry>
More information about the docs-commits
mailing list