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

man: improve description about /etc/kdump/{pre.d,post.d}interface

Browse Source 
The description is identical to the notes in kdump.conf

Signed-off-by: Pingfan Liu <piliu@redhat.com>
Acked-by: Kairui Song <kasong@redhat.com>
This commit is contained in:
Pingfan Liu 2020-06-19 11:37:02 +08:00 committed by Kairui Song
parent 61d4fa72b5
commit 6dd2b9fb41
2 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
kdump.conf.5
View File

@ -109,6 +109,11 @@ status of the current dump process is fed to the kdump_post
executable as its first argument($1). Executable can modify executable as its first argument($1). Executable can modify
it to indicate the new exit status of succeeding dump process, it to indicate the new exit status of succeeding dump process,
.PP .PP
If /etc/kdump/post.d directory exists, All files in
the directory are collectively sorted and executed in
lexical order, before binary or script specified
kdump_post parameter is executed.
.PP
Note that scripts written for use with this directive must use Note that scripts written for use with this directive must use
the /bin/bash interpreter. the /bin/bash interpreter.
.RE .RE
@ -124,6 +129,13 @@ as follows:
.PP .PP
non 0 - reboot the system non 0 - reboot the system
.PP .PP
If /etc/kdump/pre.d directory exists, all files in
the directory are collectively sorted and executed in
lexical order, after binary or script specified
kdump_pre parameter is executed.
Even if the binary or script in /etc/kdump/pre.d directory
returns non 0 exit status, the processing is continued.
.PP
Note that scripts written for this directive must use Note that scripts written for this directive must use
the /bin/bash interpreter. the /bin/bash interpreter.
.RE .RE

8
kexec-kdump-howto.txt
View File

@ -543,6 +543,9 @@ It is possible to specify a custom script or binary you wish to run following
an attempt to capture a vmcore. The executable is passed an exit code from an attempt to capture a vmcore. The executable is passed an exit code from
the capture process, which can be used to trigger different actions from the capture process, which can be used to trigger different actions from
within your post-capture executable. within your post-capture executable.
If /etc/kdump/post.d directory exist, All files in the directory are
collectively sorted and executed in lexical order, before binary or script
specified kdump_post parameter is executed.
Kdump Pre-Capture Executable Kdump Pre-Capture Executable
---------------------------- ----------------------------
@ -551,6 +554,11 @@ It is possible to specify a custom script or binary you wish to run before
capturing a vmcore. Exit status of this binary is interpreted: capturing a vmcore. Exit status of this binary is interpreted:
0 - continue with dump process as usual 0 - continue with dump process as usual
non 0 - reboot the system non 0 - reboot the system
If /etc/kdump/pre.d directory exists, all files in the directory are collectively
sorted and executed in lexical order, after binary or script specified
kdump_pre parameter is executed.
Even if the binary or script in /etc/kdump/pre.d directory returns non 0
exit status, the processing is continued.
Extra Binaries Extra Binaries
-------------- --------------