d13fd38df4
Currently "systemctl --fail --no-block default" will be executed on kdump-error-handler exit due to the config. This may makes systemd try to isolate to the default target again. The execute chain will be like: initrd.target -> kdump.sh (failed) -> kdump-error-handler.service -> failure_action -> final_action -> ExecStopPost (go to initrd.target again) Currently, reboot/shutdown/halt is called by either by executing failure_action or final_action. So the loop will be stopped. However nont of the reboot/shutdown/halt call is blocking so it might lead to race issue. Just drop the ExecStopPost to fix this potential issue. Signed-off-by: Kairui Song <kasong@redhat.com> Acked-by: Pingfan Liu <piliu@redhat.com> Tested-by: HATAYAMA Daisuke <d.hatayama@fujitsu.com>
34 lines
934 B
Desktop File
34 lines
934 B
Desktop File
# This file is part of systemd.
|
|
#
|
|
# systemd is free software; you can redistribute it and/or modify it
|
|
# under the terms of the GNU Lesser General Public License as published by
|
|
# the Free Software Foundation; either version 2.1 of the License, or
|
|
# (at your option) any later version.
|
|
|
|
# This service will run the real kdump error handler code. Executing the
|
|
# failure action configured in kdump.conf
|
|
|
|
[Unit]
|
|
Description=Kdump Error Handler
|
|
DefaultDependencies=no
|
|
After=systemd-vconsole-setup.service
|
|
Wants=systemd-vconsole-setup.service
|
|
AllowIsolate=yes
|
|
|
|
[Service]
|
|
Environment=HOME=/
|
|
Environment=DRACUT_SYSTEMD=1
|
|
Environment=NEWROOT=/sysroot
|
|
WorkingDirectory=/
|
|
ExecStart=/bin/kdump-error-handler.sh
|
|
Type=oneshot
|
|
StandardInput=tty-force
|
|
StandardOutput=inherit
|
|
StandardError=inherit
|
|
KillMode=process
|
|
IgnoreSIGPIPE=no
|
|
|
|
# Bash ignores SIGTERM, so we send SIGHUP instead, to ensure that bash
|
|
# terminates cleanly.
|
|
KillSignal=SIGHUP
|