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

kdump.conf: renew the path section

Browse Source 
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@redhat.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
This commit is contained in:
Baoquan He 2014-04-11 20:27:04 +08:00 committed by WANG Chao
parent ddeec11f09
commit d9e6603678
2 changed files with 21 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
kdump.conf
View File

@ -35,9 +35,18 @@
# such as /dev/vg/<devname>. # such as /dev/vg/<devname>.
# Otherwise it's suggested to use label or uuid. # Otherwise it's suggested to use label or uuid.
# #
# path <path> - Append path to the filesystem device which you are # path <path> - "path" represents the file system path in which
# dumping to. Ignored for raw device dumps. # vmcore will be saved. If a dump target is specified
# If unset, will default to /var/crash. # 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> # core_collector <command> <options>
# - This allows you to specify the command to copy # - This allows you to specify the command to copy

10
kdump.conf.5
View File

@ -62,7 +62,15 @@ or uuid. It's recommended to use persistent device names such as
.B path <path> .B path <path>
.RS .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. Ignored for raw device dumps. If unset, will default to /var/crash.
.RE .RE