diff --git a/kdumpctl b/kdumpctl
index 54c1cdf..ac162b5 100755
--- a/kdumpctl
+++ b/kdumpctl
@@ -246,7 +246,7 @@ function check_ssh_target()
     ssh -q -i $SSH_KEY_LOCATION -o BatchMode=yes $DUMP_TARGET mkdir -p $SAVE_PATH
     _ret=$?
     if [ $_ret -ne 0 ]; then
-        echo "Could not create $DUMP_TARGET:$SAVE_PATH, you probably need to run \"service kdump propagate\""
+        echo "Could not create $DUMP_TARGET:$SAVE_PATH, you probably need to run \"kdumpctl propagate\""
         exit $_ret
     fi
 }
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt
index 1478148..1292f7f 100644
--- a/kexec-kdump-howto.txt
+++ b/kexec-kdump-howto.txt
@@ -381,8 +381,8 @@ name or IP address of the target system. Using a dedicated, restricted user
 account on the target system is recommended, as there will be keyless ssh
 access to this account.
 
-Once kdump.conf is appropriately configured, issue the command '/sbin/service
-kdump propagate' to automatically set up the ssh host keys and transmit
+Once kdump.conf is appropriately configured, issue the command
+'kdumpctl propagate' to automatically set up the ssh host keys and transmit
 the necessary bits to the target server. You'll have to type in 'yes'
 to accept the host key for your targer server if this is the first time
 you've connected to it, and then input the target system user's password