From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Baoquan He <bhe@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Marco Elver <elver@google.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Xuefeng Li <lixuefeng@loongson.cn>,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/5] docs: kdump: add scp example to write out the dump file
Date: Tue, 8 Feb 2022 20:51:03 +0800 [thread overview]
Message-ID: <1644324666-15947-3-git-send-email-yangtiezhu@loongson.cn> (raw)
In-Reply-To: <1644324666-15947-1-git-send-email-yangtiezhu@loongson.cn>
Except cp and makedumpfile, add scp example to write out the dump file.
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Acked-by: Baoquan He <bhe@redhat.com>
---
Documentation/admin-guide/kdump/kdump.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/admin-guide/kdump/kdump.rst b/Documentation/admin-guide/kdump/kdump.rst
index d187df2..a748e7e 100644
--- a/Documentation/admin-guide/kdump/kdump.rst
+++ b/Documentation/admin-guide/kdump/kdump.rst
@@ -533,6 +533,10 @@ the following command::
cp /proc/vmcore <dump-file>
+or use scp to write out the dump file between hosts on a network, e.g::
+
+ scp /proc/vmcore remote_username@remote_ip:<dump-file>
+
You can also use makedumpfile utility to write out the dump file
with specified options to filter out unwanted contents, e.g::
--
2.1.0
next prev parent reply other threads:[~2022-02-08 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 12:51 [PATCH v2 0/5] Update doc and fix some issues about kdump Tiezhu Yang
2022-02-08 12:51 ` [PATCH v2 1/5] docs: kdump: update description about sysfs file system support Tiezhu Yang
2022-02-08 12:51 ` Tiezhu Yang [this message]
2022-02-08 12:51 ` [PATCH v2 3/5] panic: unset panic_on_warn inside panic() Tiezhu Yang
2022-02-08 13:38 ` Marco Elver
2022-02-08 12:51 ` [PATCH v2 4/5] ubsan: no need to unset panic_on_warn in ubsan_epilogue() Tiezhu Yang
2022-02-08 13:39 ` Marco Elver
2022-02-08 12:51 ` [PATCH v2 5/5] kasan: no need to unset panic_on_warn in end_report() Tiezhu Yang
2022-02-08 13:39 ` Marco Elver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1644324666-15947-3-git-send-email-yangtiezhu@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lixuefeng@loongson.cn \
--cc=ryabinin.a.a@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox