From d965a9e105fb5bdd999873ce5a4a8d31e32868b6 Mon Sep 17 00:00:00 2001 From: Dave Young Date: Fri, 31 Aug 2012 10:04:54 +0800 Subject: [PATCH] The example of nfs dump config option is wrong. s/net/nfs Signed-off-by: Dave Young Acked-by: Vivek Goyal --- kexec-kdump-howto.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt index bedb38e..574f0ce 100644 --- a/kexec-kdump-howto.txt +++ b/kexec-kdump-howto.txt @@ -364,8 +364,8 @@ or anonuid options on the NFS server side are likely of interest to permit the kdump initrd operations write to the NFS mount as root. Assuming your're exporting /dump on the machine nfs-server.example.com, -once the mount is properly configured, specify it in kdump.conf, via 'net -nfs-server.example.com:/dump'. The server portion can be specified either +once the mount is properly configured, specify it in kdump.conf, via +'nfs nfs-server.example.com:/dump'. The server portion can be specified either by host name or IP address. Following a system crash, the kdump initrd will mount the NFS mount and copy out the vmcore to your NFS server. Restart the kdump service via '/sbin/systemctl restart kdump.service' to commit this change to