Thanks for the clarification, guys.
Since this intentional, should the documentation be updated like the
following patch?
Also, who invokes kdumpctl's save_core and save_raw, which don't appear
to prefix %HOST?
-->8-- -->8--
From 412d69cd33db1f161792cdc7247b6fa2c6b93f25 Mon Sep 17 00:00:00 2001
From: Joe Lawrence <joe.lawrence(a)stratus.com>
Date: Mon, 9 Feb 2015 09:22:45 -0500
Subject: [PATCH] update documentation for local fs dump dir prefix
commit 3be6c1228e82 "change the dump dir format to be more readable"
re-added the host-ip to local fs dump destination directory (127.0.0.1).
Update relevent documentation to match.
Signed-off-by: Joe Lawrence <joe.lawrence(a)stratus.com>
Reported-by: Charlotte Richardson <charlotte.richardson(a)stratus.com>
---
kdump.conf | 2 +-
kdump.conf.5 | 2 +-
kexec-kdump-howto.txt | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/kdump.conf b/kdump.conf
index 54b581daf93b..214409429b4e 100644
--- a/kdump.conf
+++ b/kdump.conf
@@ -29,7 +29,7 @@
# /root/.ssh/kdump_id_rsa.
#
# <fs type> <partition> - Will mount -t <fs type> <partition>
/mnt and copy
-# /proc/vmcore to /mnt/var/crash/%DATE/.
+# /proc/vmcore to /mnt/var/crash/%HOST-%DATE/.
# NOTE: <partition> can be a device node, label or uuid.
# It's recommended to use persistent device names
# such as /dev/vg/<devname>.
diff --git a/kdump.conf.5 b/kdump.conf.5
index f1c2a2c1d24e..6e61227ab946 100644
--- a/kdump.conf.5
+++ b/kdump.conf.5
@@ -55,7 +55,7 @@ the default value is /root/.ssh/kdump_id_rsa.
.B <fs type> <partition>
.RS
Will mount -t <fs type> <partition> /mnt and copy /proc/vmcore to
-/mnt/var/crash/%DATE/. NOTE: <partition> can be a device node, label
+/mnt/var/crash/%HOST-%DATE/. NOTE: <partition> can be a device node, label
or uuid. It's recommended to use persistent device names such as
/dev/vg/<devname>. Otherwise it's suggested to use label or uuid.
.RE
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt
index 05b497f692e1..5c5a78e73ed4 100644
--- a/kexec-kdump-howto.txt
+++ b/kexec-kdump-howto.txt
@@ -116,8 +116,8 @@ your system by echo'ing a c into /proc/sysrq-trigger:
You should see some panic output, followed by the system restarting into
the kdump kernel. When the boot process gets to the point where it starts
the kdump service, your vmcore should be copied out to disk (by default,
-in /var/crash/<YYYY-MM-DD-HH:MM>/vmcore), then the system rebooted back into
-your normal kernel.
+in /var/crash/<HOST-IP>-<YYYY-MM-DD-HH:MM>/vmcore), then the system rebooted
+back into your normal kernel.
Once back to your normal kernel, you can use the previously installed crash
kernel in conjunction with the previously installed kernel-debuginfo to
--
1.7.10.4