Re: [Patch v2 2/2] let user specify action after systemd start dracut-emergency

[Baoquan <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>]

On 05/30/2013 05:15 PM, Harald Hoyer wrote:

>> > Hi Harald,
>> > 
>> > Since adding ConditionKernelCommandLine=!action_on_fail=continue doesn't
>> > work, do you mind applying this patch? Or do you have other suggestions?
>> > 
>> > Baoquan
>> > Thanks a lot
> Hmm, "ConditionKernelCommandLine=!action_on_fail=continue" _has_ to work.
> Otherwise I would consider that a serious bug in systemd.
> 
> Care to elaborate how you tested it?
> 
> If you are dropped to the shell, can you run:
> 
> # systemctl status dracut-emergency.service
> # systemctl status emergency.service
> 
> to confirm you are not dropped to the emergency.service, which I think this is
> the case in your test setup.
> 
> So, we have to add "ConditionKernelCommandLine=!action_on_fail=continue" to
> emergency.service, too.
> 


Hi Harald,

I added this to dracut-emergency.service, and add
action_on_fail=continue to kdump command line, then change
dracut_initqueue.sh to make the RDENTRY=0, then mount won't succeed.

From my side, the ConditionKernelCommandLine=!action_on_fail=continue
doesn't work.

And I also tried ConditionKernelCommandLine=action_on_fail=continue, but
remove the kdump command line action_on_fail=continue, it didn't work
either.


Baoquan
Thanks a lot