[deployment-guide] Adjusted service and chkconfig commands.
Jaromir Hradilek
jhradile at fedoraproject.org
Mon May 23 21:36:11 UTC 2011
commit bd4de2ea508a67c1921f36b74dd808c030e772cd
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Mon May 23 20:03:13 2011 +0200
Adjusted service and chkconfig commands.
en-US/Network_Interfaces.xml | 19 +++----------------
en-US/PackageKit.xml | 5 +----
en-US/SSSD.xml | 8 ++++----
en-US/The_kdump_Crash_Recovery_Service.xml | 11 +++++------
en-US/The_sysconfig_Directory.xml | 4 ++--
5 files changed, 15 insertions(+), 32 deletions(-)
---
diff --git a/en-US/Network_Interfaces.xml b/en-US/Network_Interfaces.xml
index 889cf35..f6e965a 100644
--- a/en-US/Network_Interfaces.xml
+++ b/en-US/Network_Interfaces.xml
@@ -852,14 +852,6 @@ IDLETIMEOUT=600</screen>
</indexterm>
<indexterm
significance="normal">
- <primary>network</primary>
- <secondary>commands</secondary>
- <tertiary>
- <command>/sbin/service network</command>
- </tertiary>
- </indexterm>
- <indexterm
- significance="normal">
<primary>
<command>ifup</command>
</primary>
@@ -998,16 +990,11 @@ IDLETIMEOUT=600</screen>
<title>Be careful when removing or modifying network scripts!</title>
<para>Removing or modifying any scripts in the <filename>/etc/sysconfig/network-scripts/</filename> directory can cause interface connections to act irregularly or fail. Only advanced users should modify scripts related to a network interface.</para>
</warning>
- <para>The easiest way to manipulate all network scripts simultaneously is to use the <command>/sbin/service</command> command on the network service (<filename>/etc/rc.d/init.d/network</filename>), as illustrated the following command:</para>
- <screen>
-<command>/sbin/service network <replaceable><action></replaceable>
- </command>
- </screen>
+ <para>The easiest way to manipulate all network scripts simultaneously is to use the <command>systemctl</command> command on the network service (<filename>/etc/rc.d/init.d/network</filename>), as illustrated the following command:</para>
+ <screen><command>systemctl <replaceable><action> network.service</replaceable></command></screen>
<para><!-- RHEL5: In this example -->Here, <replaceable><action></replaceable> can be either <command>start</command>, <command>stop</command>, or <command>restart</command>.</para>
<para>To view a list of configured devices and currently active network interfaces, use the following command:</para>
- <screen>
-<command>/sbin/service network status</command>
- </screen>
+ <screen><command>service network status</command></screen>
</section>
<section
id="s1-networkscripts-static-routes">
diff --git a/en-US/PackageKit.xml b/en-US/PackageKit.xml
index e356ed8..d13b56f 100644
--- a/en-US/PackageKit.xml
+++ b/en-US/PackageKit.xml
@@ -588,10 +588,7 @@
</tbody>
</tgroup>
</table>
- <para>The <command>packagekitd</command> daemon runs outside the user session and communicates with the various graphical front ends. The <command>packagekitd</command> daemon<footnote
- id="footnote-Daemons"><para>System daemons are typically long-running processes that provide services to the user or to other programs, and which are started, often at boot time, by special initialization scripts (often shortened to <emphasis>init scripts</emphasis>). Daemons respond to the <command>service</command> command and can be turned on or off permanently by using the <command>chkconfig on</command> or <command>chkconfig off</command>commands. They can typically be recognized by a <quote><emphasis>d</emphasis>
- </quote> appended to their name, such as the <command>packagekitd</command> daemon. Refer to <xref
- linkend="ch-Services_and_Daemons"/> for information about system services.</para>
+ <para>The <command>packagekitd</command> daemon runs outside the user session and communicates with the various graphical front ends. The <command>packagekitd</command> daemon<footnote id="footnote-Daemons"><para>System daemons are typically long-running processes that provide services to the user or to other programs, and which are started, often at boot time. Daemons respond to the <command>systemctl</command> command and can be turned on or off permanently by using the <command>systemctl enable</command> or <command>systemctl disable</command>commands. They can typically be recognized by a <quote><emphasis>d</emphasis></quote> appended to their name, such as the <command>packagekitd</command> daemon. Refer to <xref linkend="ch-Services_and_Daemons"/> for information about system services.</para>
</footnote>
communicates via the <application>DBus</application> system message bus with another back end, which utilizes <application>Yum</application>'s Python API to perform queries and make changes to the system. On Linux systems other than Red Hat and Fedora, <command>packagekitd</command> can communicate with other back ends that are able to utilize the native package manager for that system. This modular architecture provides the abstraction necessary for the graphical interfaces to work with many different package managers to perform essentially the same types of package management tasks. Learning how to use the <application>PackageKit</application> front ends means that you can use the same familiar graphical interface across many different Linux distributions, even when they utilize a native package manager other than <application>Yum</application>.</para>
<para>In addition, <application>PackageKit</application>'s separation of concerns provides reliability in that a crash of one of the GUI windows—or even the user's X Window session—will not affect any package management tasks being supervised by the <command>packagekitd</command> daemon, which runs outside of the user session.</para>
diff --git a/en-US/SSSD.xml b/en-US/SSSD.xml
index 06c9265..f5ed070 100644
--- a/en-US/SSSD.xml
+++ b/en-US/SSSD.xml
@@ -255,11 +255,11 @@
</note>
<para>You can use either the <command>service</command> command or the <filename>/etc/init.d/sssd</filename> script to control SSSD. For example, run the following command to start <systemitem class="daemon">sssd</systemitem>:</para>
<para>
- <command># service sssd start</command>
+ <command># systemctl start sssd.service</command>
</para>
- <para>By default, SSSD is configured not to start automatically. There are two ways to change this behavior; if you use the Authentication Configuration tool to configure SSSD, it will reconfigure the default behavior so that SSSD starts when the machine boots. Alternatively, you can use the <command>chkconfig</command> command, as follows:</para>
+ <para>By default, SSSD is configured not to start automatically. There are two ways to change this behavior; if you use the Authentication Configuration tool to configure SSSD, it will reconfigure the default behavior so that SSSD starts when the machine boots. Alternatively, you can use the <command>systemctl</command> command, as follows:</para>
<para>
- <command># chkconfig sssd on</command>
+ <command># systemctl enable sssd.service</command>
</para>
</section>
@@ -1711,7 +1711,7 @@ GroupE:*:518:UserE
<listitem>
<para>Ensure that NSS is running</para>
<para>
- <command># service sssd status</command>
+ <command># systemctl is-active sssd.service</command>
</para>
<para>This command should return results similar to the following:</para>
<screen>sssd (pid 21762) is running...
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 2a2d939..8c338b9 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -608,15 +608,15 @@ path /usr/local/cores</screen>
<para>
To start the <systemitem class="service">kdump</systemitem> daemon at boot time, type the following at a shell prompt:
</para>
- <screen><command>chkconfig kdump on</command></screen>
+ <screen><command>systemctl enable kdump.service</command></screen>
<para>
- This will enable the service for runlevels <literal>2</literal>, <literal>3</literal>, <literal>4</literal>, and <literal>5</literal>. Similarly, typing <command>chkconfig kdump off</command> will disable it for all runlevels. To start the service in the current session, use the following command:
+ Similarly, typing <command>systemctl disable kdump.service</command> will disable it. To start the service in the current session, use the following command:
</para>
<indexterm>
<primary><systemitem class="service">kdump</systemitem></primary>
<secondary>running the service</secondary>
</indexterm>
- <screen><command>service kdump start</command></screen>
+ <screen><command>systemctl start kdump.service</command></screen>
<para>
For more information on runlevels and configuring services in general, refer to <xref linkend="ch-Services_and_Daemons" />.
</para>
@@ -635,10 +635,9 @@ path /usr/local/cores</screen>
</para>
</warning>
<para>
- To test the configuration, reboot the system with <systemitem class="service">kdump</systemitem> enabled, and make sure that the service is running (refer to <xref linkend="s1-services-running" /> for more information on how to run a service in &MAJOROS;). For example:
+ To test the configuration, reboot the system with <systemitem class="service">kdump</systemitem> enabled, and make sure that the service is running (refer to <xref linkend="s1-services-running" /> for more information on how to run a service in &MAJOROS;):
</para>
- <screen>~]# <command>service kdump status</command>
-Kdump is operational</screen>
+ <screen><command>systemctl is-active kdump.service</command></screen>
<para>
Then type the following commands at a shell prompt:
</para>
diff --git a/en-US/The_sysconfig_Directory.xml b/en-US/The_sysconfig_Directory.xml
index 3474017..9bc29be 100644
--- a/en-US/The_sysconfig_Directory.xml
+++ b/en-US/The_sysconfig_Directory.xml
@@ -685,9 +685,9 @@
<note>
<title>You can run the firstboot program again</title>
<para>
- To start the <command>firstboot</command> program the next time the system boots, change the value of <command>RUN_FIRSTBOOT</command> option to <option>YES</option>, and type the following at a shell prompt:
+ To start the <command>firstboot</command> program the next time the system boots, change the value of <command>RUN_FIRSTBOOT</command> option to <option>YES</option>, and type the following at a shell prompt as <systemitem class="username">root</systemitem>:
</para>
- <screen>~]# <command>chkconfig firstboot on</command>
+ <screen>~]# <command>systemctl enable firstboot.service</command>
</screen>
</note>
</section>
More information about the docs-commits
mailing list