Encrypted target have many issues, so let user check kexec-kdump-howto.txt, which have more details.
Signed-off-by: Kairui Song kasong@redhat.com --- mkdumprd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mkdumprd b/mkdumprd index 91ce3d5..36f71b7 100644 --- a/mkdumprd +++ b/mkdumprd @@ -400,7 +400,7 @@ if ! check_resettable; then fi
if ! check_crypt; then - echo "Warning: Encrypted device is in dump path. User will prompted for password during second kernel boot." + echo "Warning: Encrypted device is in dump path, which is not recommended, see kexec-kdump-howto.txt for more details." fi
# firstly get right SSH_KEY_LOCATION
On 08/06/2020 01:39 PM, Kairui Song wrote:
Encrypted target have many issues, so let user check kexec-kdump-howto.txt, which have more details.
Signed-off-by: Kairui Song kasong@redhat.com
mkdumprd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mkdumprd b/mkdumprd index 91ce3d5..36f71b7 100644 --- a/mkdumprd +++ b/mkdumprd @@ -400,7 +400,7 @@ if ! check_resettable; then fi
if ! check_crypt; then
- echo "Warning: Encrypted device is in dump path. User will prompted for password during second kernel boot."
- echo "Warning: Encrypted device is in dump path, which is not recommended, see kexec-kdump-howto.txt for more details."
fi
# firstly get right SSH_KEY_LOCATION
Acked-by: Pingfan Liu piliu@redhat.com