Users Guide
or
Run the command: "gnome-tweak-tool", and then go to Power settings > Suspend & Power button
actions for "When Power Button is pressed"
• Execute the following commands with root privileges:
a gsettings set org.gnome.settings-daemon.plugins.power button-power
shutdown
or
gsettings set org.gnome.settings-daemon.plugins.power power-button-
action 'interactive'
b dconf update
• Change the default behavior using the following steps:
a Create a le using /etc/dconf/db/local.d/01-power with the following contents:
[org/gnome/settings-daemon/plugins/power]
button-sleep='nothing'
button-suspend='nothing'
button-hibernate='nothing'
button-power='shutdown'
b Create a le using /etc/dconf/db/local.d/locks/01-power with the following contents:
/org/gnome/settings-daemon/plugins/power/button-sleep
/org/gnome/settings-daemon/plugins/power/button-suspend
/org/gnome/settings-daemon/plugins/power/button-hibernate
/org/gnome/settings-daemon/plugins/power/button-power
c Run the command: dconf update
d User must log out and log in again before the system-wide settings take eect.
NOTE
: The above workaround may not work when the system is locked. GNOME prevents the accidental shutdown when
system is locked. As a security precaution, GNOME does not allow any power related actions such as shutdown from any system
management interfaces like iDRAC or pressing the power button unless the user is active and logged in OS.
NOTE: The preceding steps are not applicable to RHEL 7.4. The workaround for RHEL 7.4 is to install the acpid package, and
replace /etc/acpi/actions/power.sh content with the following content:
#!/bin/sh
PATH=/usr/sbin:/usr/bin
shutdown -h now
Kernel panic occurs when OMSA services are started
on Red Hat Enterprise Linux 7
Description:
Kernel panic occurs when OpenManage Server Administrator (OMSA) services are started on Red Hat Enterprise
Linux 7.
Applies to: Red Hat Enterprise Linux 7.0
Cause: The Kernel might spend more time in servicing the kernel timer functions and set a ag to prevent the other code
from resetting the timer hardware (APIC timer). Then it programs the timer hardware for a timeout up to 100
milliseconds to run the kernel timer functions. At the next timer hardware interrupt, this ag is cleared. However,
there is a bug in the kernel where this ag can be ignored in one specic code path. When this happens, the timer
hardware can be set to the wrong timeout value. This incorrect timeout value can be over 10 seconds during this
time no kernel timer function runs.
Workaround: Update the kernel to Z-stream kernel.
14 Issues or limitations before installation