Attachment 843622 Details for Bug 1047428 – This patch corrects the reported issue.

[patch] This patch corrects the reported issue.

0001-Update-commands-for-starting-stopping-and-checking-t.patch (text/plain), 3.47 KB, created by Pete Travis on 2013-12-31 05:46:23 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Pete Travis

Created: 2013-12-31 05:46:23 UTC

Size: 3.47 KB

patch

obsolete

>From a6419e00b515765085cc4e646c3822ebdda607df Mon Sep 17 00:00:00 2001
>From: Pete Travis <immanetize@fedoraproject.org>
>Date: Mon, 30 Dec 2013 21:52:57 -0700
>Subject: [PATCH] Update commands for starting, stopping, and checking the
> status of abrtd to use systemctl instead of service/chkconfig
>
>---
> en-US/Automatic_Bug_Reporting_Tool_ABRT.xml | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
>diff --git a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
>index 1093dc8..f01bb33 100644
>--- a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
>+++ b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
>@@ -88,18 +88,18 @@
>       Your next step should be to verify that <systemitem
>         class="daemon">abrtd</systemitem> is running. The daemon is typically configured to start up at boot time. You can use the following command as root to verify its current status:
>     </para>
>-    <screen>~]#&#160;<command>service abrtd status</command>
>+    <screen>~]#&#160;<command>systemctl status abrtd</command>
> abrtd (pid 1535) is running...</screen>
>     <para>
>-      If the <command>service</command> command returns the <computeroutput>abrt is stopped</computeroutput> message, the daemon is not running. It can be started for the current session by entering this command:
>+      If the <command>systemctl</command> command returns the <computeroutput>Active: inactive (dead)</computeroutput> message, the daemon is not running. It can be started for the current session by entering this command:
>     </para>
>-    <screen>~]#&#160;<command>service abrtd start</command>
>+    <screen>~]#&#160;<command>systemctl start abrtd </command>
> Starting abrt daemon:                                      [  OK  ]</screen>
>     <para>
>-      You can run the following <command>chkconfig</command> command to ensure that the <systemitem
>+      You can run the following <command>systemctl</command> command to ensure that the <systemitem
>         class="daemon">abrtd</systemitem> service initializes every time the system starts up:
>     </para>
>-    <screen>~]#&#160;<command>chkconfig abrtd on</command></screen>
>+    <screen>~]#&#160;<command>systemctl enable abrtd </command></screen>
>     <para>
>       Similarly, you can follow the same steps to check and configure the <systemitem
>         class="service">abrt-ccpp</systemitem> service if you want <application>ABRT</application> to catch C/C++ crashes. To set <application>ABRT</application> to detect kernel oopses, use the same steps for the <systemitem
>@@ -119,12 +119,12 @@ kernel.panic = 0</screen>
>     <para>
>       Finally, you can verify that the <systemitem
>         class="service">ABRT notification applet</systemitem> is running:
>-    </para>
>-    <screen>~]$ <command>ps -el | grep abrt-applet</command>
>+  </para>
>+  <screen>~]$ <command>ps -el | grep abrt-applet</command>
> 0 S   500  2036  1824  0  80   0 - 61604 poll_s ?        00:00:00 abrt-applet</screen>
>-    <para>
>-      If the <application>ABRT</application> notification applet is not running, you can start it manually in your current desktop session by running the <systemitem
>-        class="service">abrt-applet</systemitem> program:
>+  <para>
>+    If the <application>ABRT</application> notification applet is not running, you can start it manually in your current desktop session by running the <systemitem
>+      class="service">abrt-applet</systemitem> program:
>     </para>
>     <screen>~]$ <command>abrt-applet &amp;</command>
> [1] 2261</screen>
>-- 
>1.8.4.2

Actions: View | Diff

Attachments on bug 1047428: 843622