[Patch v5 6/6] kdump.conf: renew the path section

[Baoquan He]

In case no target is specified explicitly in /etc/kdump.conf, the behavior
of path is changed, a check need be taken to see if any separate file
system is mounted on any tier of 'path', and also to take the relevant
action. Now the path section need be renewed for kdump.conf and its
man page accordingly.

Signed-off-by: Baoquan He <bhe at redhat.com>
---
 kdump.conf   | 15 ++++++++++++---
 kdump.conf.5 | 10 +++++++++-
 2 files changed, 21 insertions(+), 4 deletions(-)

diff --git a/kdump.conf b/kdump.conf
index a106462..d6f1123 100644
--- a/kdump.conf
+++ b/kdump.conf
@@ -35,9 +35,18 @@
 #			  such as /dev/vg/<devname>.
 #			  Otherwise it's suggested to use label or uuid.
 #
-# path <path> 		- Append path to the filesystem device which you are
-#			  dumping to.  Ignored for raw device dumps.
-#		 	  If unset, will default to /var/crash.
+# path <path> 		- "path" represents the file system path in which
+#                         vmcore will be saved. If a dump target is specified
+#                         in kdump.conf, then "path" is relative to the
+#                         specified dump target. Interpretation of path
+#                         changes a bit if user has not specified a dump
+#                         target explicitly in kdump.conf. In this case, 
+#                         "path" represents the absolute path from root.
+#                         And dump target and adjusted path are arrived
+#                         at automatically depending on what's mounted
+#                         in the current system.
+#                         Ignored for raw device dumps.  If unset, will
+#                         default to /var/crash.
 #
 # core_collector <command> <options>
 #			- This allows you to specify the command to copy
diff --git a/kdump.conf.5 b/kdump.conf.5
index 7eaf9dd..c338342 100644
--- a/kdump.conf.5
+++ b/kdump.conf.5
@@ -62,7 +62,15 @@ or uuid.  It's recommended to use persistent device names such as
 
 .B path <path>
 .RS
-Append path to the filesystem device which you are dumping to.
+"path" represents the file system path in which vmcore will be saved.
+If a dump target is specified in kdump.conf, then "path" is relative to the
+specified dump target.
+.PP
+Interpretation of path changes a bit if user has not specified a dump
+target explicitly in kdump.conf. In this case, "path" represents the
+absolute path from root. And dump target and adjusted path are arrived
+at automatically depending on what's mounted in the current system.
+.PP
 Ignored for raw device dumps.  If unset, will default to /var/crash.
 .RE
 
-- 
1.8.5.3