9e964ff4c6
Upon encountering a failure, dracut can drop user to emergency shell. But in kdump environment kdump module wants to do the error handling and wants to handle error as sepecified by user in kdump.conf file (halt, reboot etc). Now dracut has provided an option action_on_fail=continue which means dracut just ignores the failure and continues and expects module to handle the error. Modify kdump.sysconfig to pass action_on_fail=continue to dracut. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Baoquan He <bhe@redhat.com> Acked-by: WANG Chao <chaowang@redhat.com> Acked-by: Vivek Goyal <vgoyal@redhat.com> |
||
---|---|---|
po | ||
.gitignore | ||
98-kexec.rules | ||
dracut-kdump.sh | ||
dracut-module-setup.sh | ||
dracut-monitor_dd_progress | ||
firstboot_kdump.py | ||
kdump.conf | ||
kdump.conf.5 | ||
kdump.init | ||
kdump.service | ||
kdump.sysconfig | ||
kdump.sysconfig.i386 | ||
kdump.sysconfig.ia64 | ||
kdump.sysconfig.ppc64 | ||
kdump.sysconfig.s390x | ||
kdump.sysconfig.x86_64 | ||
kdumpctl | ||
kexec-kdump-howto.txt | ||
kexec-tools-2.0.3-build-makedumpfile-eppic-shared-object.patch | ||
kexec-tools-2.0.3-disable-kexec-test.patch | ||
kexec-tools.spec | ||
mkdumprd | ||
mkdumprd.8 | ||
rhcrashkernel-param | ||
sources | ||
zanata-notes.txt |