On Wed, May 07, 2014 at 05:51:55PM +0800, Dave Young wrote:
Hi, Chao and Vivek
As far as I understand your new error handler will jump into kdump.sh in
case any error in systemd. It will fix most of the problems. But there will
be limitation for new error handler service that dump_to_rootfs will always
fail in case error happens before entering kdump.sh.
Once an error happens in the system, there are no guarantees what will
work and what will not.
So why will dump_to_rootfs will not work? Because we have stopped rest
of the services?
>From the thread link you sent about systemd discussion, they proposed below
solution:
http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/18278
It will create a local-fs-all.target for us to wait them, I'd like to know
what's the conclusion, why can't we do this way?
What's the advantage of this proposal? I think it is just making things
more twisted and complicated. That is first we are forced to pass "nofail"
option and then create extra targets which wait for dependencies to
finish.
Possiblly there's other fail point other than fsck/mount in systemd which
we can not catch, is this the reason we ignore the proposal?
I think that proposal is complicated that's why I suggested a simpler
way.
So can you please explain that why that proposal is better and why
we should do things that way.
Thanks
Vivek