From: Freeman Zhang <freeman.zhang1992-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ronit Halder <ronit.crj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
ronit.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernelnewbies-7JyXY6prKcjpASu1u0TL5ti2O/JbrIOy@public.gmane.org,
zhezhang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: "kdumpbase" dracut module
Date: Tue, 22 Mar 2016 08:41:21 +0800 [thread overview]
Message-ID: <56F094B1.6070209@gmail.com> (raw)
In-Reply-To: <CAAm8cU6EaVwQPV5wwy5PXeEShtEfscTz-vAOOxmZWP56YDgNSg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 483 bytes --]
On 3/21/16 9:55 PM, Ronit Halder wrote:
> Thanks for helping
>
> So, this module is used to dump the crash kernel.
> Am I right?
> If not then can you explain how kdump kernel calls the makedumpfile?
>
You are absolutely right Ronit. By the time the second kernel is booted,
this module will start a service called kdump-capture, which will
execute kdump.sh, which will invoke makedumpfile after all, depending on
your kdump configuration.
All the best!
Freeman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
prev parent reply other threads:[~2016-03-22 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 7:29 "kdumpbase" dracut module Ronit Halder
[not found] ` <CACeEjSL0jrqF9WtX3mZrO0036pGc4O4aPg+=JPMOB7QH47DLWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-21 6:26 ` Dave Young
[not found] ` <20160321062655.GA9896-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2016-03-21 13:55 ` Ronit Halder
[not found] ` <CAAm8cU6EaVwQPV5wwy5PXeEShtEfscTz-vAOOxmZWP56YDgNSg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-22 0:41 ` Freeman Zhang [this message]
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=56F094B1.6070209@gmail.com \
--to=freeman.zhang1992-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernelnewbies-7JyXY6prKcjpASu1u0TL5ti2O/JbrIOy@public.gmane.org \
--cc=ronit.crj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ronit.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=zhezhang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
/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