Red Hat Bugzilla – Bug 1015033
acpid doesn't have its own entry in the /etc/sysconfig directory
Last modified: 2016-02-16 16:11:33 EST
Description of problem:
It's expected for a system administrator to know if someone has pressed (in)voluntarily the power button, which in turn forced (in the majority of cases) an unexpected server shutdown.
The acpid daemon needs the command line argument '-l, --logevents' to log information about all events and actions (including those related to button/power) in the syslog.
Currently the only way to include such argument is editing its SysVinit script which makes the solution ineffective because the changes will disappear in the next acpid update, forcing the system administrator to memorize those changes before the update.
The most elegant way would be if the acpid had its own file in the /etc/sysconfig/ directory which would be read by the SysVinit script during the start.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create and edit the file /etc/sysconfig/acpid to include the line:
2. Restart acpid with 'service acpid restart'.
3. Press the power button in the server.
The event is not logged in syslog.
The event is logged in syslog.
Created attachment 809864 [details]
(In reply to Jaroslav Škarvada from comment #3)
> Created attachment 809864 [details]
> Proposed fix
Thanks for accepting the suggestion and for your quick fix.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Looks good to me. Test result can be found here: https://beaker.engineering.redhat.com/jobs/1206704
I'm setting it to verified.
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.