Unnamed repository
b4b0a27d8a
In old code, kdumpctl program exit directly when check_ssh_target failed without printing "Starting kdump: FAILED". Then when manually invoke "kdumpctl restart", only print "Stopping kdump: OK", but no "Starting kdump: FAILED". That is unreasonable. In this patch change check_ssh_target() to return when it failed. Then check the returned value in start() function and print status if the returned value is not 0. Meanwhile change "space" to "tab" in function check_ssh_target(), make those be consistent with the whole script file. Signed-off-by: Baoquan He <bhe@redhat.com> Acked-by: Dave Young <dyoung@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-disable-kexec-test.patch | ||
kexec-tools-2.0.3-kdump-pass-acpi_rsdp-to-2nd-kernel-for-efi-booting.patch | ||
kexec-tools-2.0.3-Load-bzImages-smaller-than-32-KiB.patch | ||
kexec-tools-2.0.3-ppc-exec-stack-fix.patch | ||
kexec-tools-2.0.3-ppc-ppc64-compile-purgatory-code-with-gcc-option-msoft-float.patch | ||
kexec-tools-2.0.3-vmcore-dmesg-Do-not-write-beyond-end-of-buffer.patch | ||
kexec-tools-2.0.3-vmcore-dmesg-vmcore-dmesg-Make-it-work-with-new-stru.patch | ||
kexec-tools.spec | ||
mkdumprd | ||
mkdumprd.8 | ||
rhcrashkernel-param | ||
sources | ||
zanata-notes.txt |