Description of problem:
/etc/init.d/abrt-ccpp status returns nothing because
of verbose=false setting in /usr/sbin/abrt-install-ccpp-hook.
Version-Release number of selected component (if applicable):
abrt-2.0.8-4.el6 (from RHEL6.3 beta)
abrt-addon-ccpp-2.0.8-4.el6. (from RHEL6.3 beta)
Steps to Reproduce:
1. Install RHEL6.3 beta
2. Login to the system with root user
3. Check abrtd is running ( ps ax |grep abrt)
This one is auto starting while booting the OS.
4. Manually start abrt-ccpp ( # /etc/init.d/abrt-ccpp start)
5. Manually check abrt-ccpp is running or not. (# /etc/init.d/abrt-ccpp status)
It returns nothing.
Some messages which indicates abrt-ccpp is working or not should be display.
After modify verbose=false to true in /usr/sbin/abrt-install-ccpp-hook,
either "Installed" or "Not installed" are display.
From user's point of view, I wanted to checkout what kind of process is running
for abrt-ccpp servoce , and try " ps ax |grep abrt" but I couldn't find
the "abrt-ccpp" daemon. And "abrt-ccpp status" returns nothing.
This is very confused.
Then I followed the script and learned that the script "installed" the hook,
instead of starting some daemon.
I hope this is documented somewhere (ex. Update Deployment Guide or KB.)
If we can find the good documentation, I don't request to modify the default
setting. (And ask the customer to read the manual before making a question.)
Business impact: None
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Fixed in git:
Author: Denys Vlasenko <firstname.lastname@example.org>
Date: Sun Jul 29 22:19:29 2012 +0200
Make "abrt-ccpp status" tell user whether hook is currently installed
*** Bug 854623 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.