From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
WANG Chao <chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] Change the implementation of action_on_fail
Date: Wed, 31 Jul 2013 16:25:57 +0200 [thread overview]
Message-ID: <51F91E75.3070102@redhat.com> (raw)
In-Reply-To: <20130731142050.GG31151-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 07/31/2013 04:20 PM, Vivek Goyal wrote:
> On Wed, Jul 31, 2013 at 04:07:16PM +0200, Harald Hoyer wrote:
>> On 07/23/2013 12:16 PM, Baoquan He wrote:
>>> Currently when action_on_fail is enabled, the emergency_shell won't be called.
>>> In kdump even though user specify the default action as emergency_shell,
>>> dracut skip it. Now change the implementation of action_on_fail to depend
>>> on a file which is created by kdump when making kdump initrd, then remove it
>>> at the beginning of kdump. This can solve the explicit emergency_shell problem.
>>>
>>> And action_on_fail won't need paramenters, remove the relevant description in
>>> dracut man page.
>>
>> I like it.
>>
>> Vivek: would that solve one of your systemd problems?
>
> Hi Harald,
>
> Yes this should solve one of the problems of being able to call emergency
> shell from kdump module.
>
> I was thinking of modirying emergency.service on the fly and then reload
> systemd config. But I guess this solution is simpler.
>
> It also takes away the flexibility of being able to specify "reboot" or
> some other actions as failure actions. But nobody as asked for those
> yet.
>
> So yes, agreed, this will solve atleast one problem. So makes sense
> to take it in.
>
> Thanks
> Vivek
>
pushed, thanks!
next prev parent reply other threads:[~2013-07-31 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 10:16 [PATCH] Change the implementation of action_on_fail Baoquan He
[not found] ` <73cc07330929ba4b226f2a0623a5459cd42932b9.1374574542.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-23 10:25 ` Baoquan
2013-07-31 14:07 ` Harald Hoyer
[not found] ` <51F91A14.4020601-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-31 14:20 ` Vivek Goyal
[not found] ` <20130731142050.GG31151-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-31 14:25 ` Harald Hoyer [this message]
[not found] ` <51F91E75.3070102-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-31 14:29 ` Vivek Goyal
[not found] ` <20130731142905.GH31151-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-31 14:31 ` Harald Hoyer
[not found] ` <51F91FAC.50706-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-08-01 14:24 ` Baoquan He
[not found] ` <20130801142445.GB8230-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-08-01 14:54 ` Vivek Goyal
2013-08-01 14:54 ` WANG Chao
2013-07-31 14:27 ` Vivek Goyal
2013-08-01 13:48 ` Vivek Goyal
-- strict thread matches above, loose matches on Subject: below --
2013-07-22 11:32 Baoquan He
[not found] ` <8a7ac3492f63fd2a5fa7ee57d9b9e7c8c2dd305c.1374492675.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-23 9:53 ` Baoquan
2013-07-23 10:14 ` Baoquan
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=51F91E75.3070102@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vgoyal-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