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

The example of nfs dump config option is wrong.

Browse Source 
s/net/nfs

Signed-off-by: Dave Young <dyoung@redhat.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
This commit is contained in:
Dave Young 2012-08-31 10:04:54 +08:00
parent 1053f9b7d2
commit d965a9e105
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
kexec-kdump-howto.txt
View File

@ -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. the kdump initrd operations write to the NFS mount as root.
Assuming your're exporting /dump on the machine nfs-server.example.com, 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 once the mount is properly configured, specify it in kdump.conf, via
nfs-server.example.com:/dump'. The server portion can be specified either '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 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 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 kdump service via '/sbin/systemctl restart kdump.service' to commit this change to