diff --git a/kdump.conf b/kdump.conf
index faa957e..308a9a8 100644
--- a/kdump.conf
+++ b/kdump.conf
@@ -38,28 +38,10 @@
 #			  as the initrd will automatically be populated with
 #			  a config file appropriate for the running kernel.
 #
-# kdump_post <binary | script>
-# 			- This directive allows you to run a specified
-# 			  executable just after the memory dump process
-# 			  terminates. The exit status from the dump process
-# 			  is fed to the kdump_post executable, which can be
-# 			  used to trigger different actions for success or
-# 			  failure.
-#
-# kdump_pre <binary | script>
-#			- works just like the kdump_post directive, but instead
-#			  of running after the dump process, runs immediately
-#			  before.  Exit status of this binary is interpreted
-#			  as follows:
-#			  0 - continue with dump process as usual
-#			  non 0 - reboot/halt the system
-#
 # extra_bins <binaries | shell scripts>
 # 			- This directive allows you to specify additional
 # 			  binaries or shell scripts you'd like to include in
-# 			  your kdump initrd. Generally only useful in
-# 			  conjunction with a kdump_post binary or script that
-# 			  relies on other binaries or scripts.
+# 			  your kdump initrd.
 #
 # extra_modules <module(s)>
 # 			- This directive allows you to specify extra kernel
@@ -96,7 +78,6 @@
 #sshkey /root/.ssh/kdump_id_rsa
 #path /var/crash
 #core_collector makedumpfile -c
-#kdump_post /var/crash/scripts/kdump-post.sh
 #extra_bins /usr/bin/lftp
 #disk_timeout 30
 #extra_modules gfs2
diff --git a/kdump.conf.5 b/kdump.conf.5
index 39ab01a..cb91d0b 100644
--- a/kdump.conf.5
+++ b/kdump.conf.5
@@ -76,41 +76,11 @@ here, as the initrd will automatically be populated with a config file
 appropriate for the running kernel.
 .RE
 
-.B kdump_post <binary | script>
-.RS
-This directive allows you to run a specified
-executable just after the memory dump process
-terminates. The exit status from the dump process
-is fed to the kdump_post executable, which can be
-used to trigger different actions for success or
-failure.
-.PP
-Note that scripts written for use with this
-directive must use the /bin/msh interpreter
-.RE
-
-.B kdump_pre <binary | script>
-.RS
-Works just like the kdump_post directive, but instead
-of running after the dump process, runs immediately
-before.  Exit status of this binary is interpreted
-as follows:
-.PP
-0 - continue with dump process as usual
-.PP
-non 0 - reboot/halt the system
-.PP
-Note that scripts written for this directive must use 
-the /bin/msh interpreter
-.RE
-
 .B extra_bins <binaries | shell scripts>
 .RS
 This directive allows you to specify additional
 binaries or shell scripts you'd like to include in
-your kdump initrd. Generally only useful in
-conjunction with a kdump_post binary or script that
-relies on other binaries or scripts.
+your kdump initrd.
 .RE
 
 .B extra_modules <module(s)>
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt
index 2254ce8..c5c8cf3 100644
--- a/kexec-kdump-howto.txt
+++ b/kexec-kdump-howto.txt
@@ -403,20 +403,11 @@ example, 'path /data/coredumps' would lead to vmcore files being written to
 that the path option is ingnored if your kdump configuration results in the
 core being saved from the initscripts in the root filesystem.
 
-Kdump Post-Capture Executable
-
-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 
-the capture process, which can be used to trigger different actions from
-within your post-capture executable.
-
 Extra Binaries
 
 If you have specific binaries or scripts you want to have made available
 within your kdump initrd, you can specify them by their full path, and they
 will be included in your kdump initrd, along with all dependent libraries.
-This may be particularly useful for those running post-capture scripts that
-rely on other binaries.
 
 Extra Modules