rpms/kexec-tools
7
0
Fork 0
Code Issues Pull Requests Releases Activity

mkfadumprd: drop unset globals from debug output

Browse Source 
mkfadumprd doesn't call prepare_kdump_bootinfo from kdump-lib.sh. Thus
both KDUMP_KERNELVER and DEFAULT_INITRD are always empty. Simply remove
them from the debug print.

Signed-off-by: Philipp Rudo <prudo@redhat.com>
Reviewed-by: Coiby Xu <coxu@redhat.com>
This commit is contained in:
Philipp Rudo 2023-01-12 16:31:03 +01:00 committed by Coiby Xu
parent b9fd7a4076
commit 383cb62202
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
mkfadumprd Normal file → Executable file
View File

@ -37,7 +37,7 @@ FADUMP_INITRD="$MKFADUMPRD_TMPDIR/fadump.img"
### First build an initramfs with dump capture capability ### First build an initramfs with dump capture capability
# this file tells the initrd is fadump enabled # this file tells the initrd is fadump enabled
touch "$MKFADUMPRD_TMPDIR/fadump.initramfs" touch "$MKFADUMPRD_TMPDIR/fadump.initramfs"
ddebug "rebuild fadump initrd: $FADUMP_INITRD $DEFAULT_INITRD $KDUMP_KERNELVER" ddebug "rebuild fadump initrd: $FADUMP_INITRD"
# Don't use squash for capture image or default image as it negatively impacts # Don't use squash for capture image or default image as it negatively impacts
# compression ratio and increases the size of the initramfs image. # compression ratio and increases the size of the initramfs image.
# Don't compress the capture image as uncompressed image is needed immediately. # Don't compress the capture image as uncompressed image is needed immediately.