Eric W. Biederman wrote: > >You can put anything you want for crash_kexec to execute. > >If the problem is strictly limited to hardware failure and software >can cope with that then don't panic the kernel and execute an orderly >transition. > >If software cannot cope, and must panic the kernel it clearly cannot >do something sensible. > >Eric > > >
Something like out of memory and oops-es are enough to deeme the system must panic because it is simply not supposed to happen in a Telco server at any time. kdump helps debugging these cases, but more importantly another server must take over the work, and this has and always will have highest priority. I'm happy about what crash_kexec does today, but the timing issue makes it unusable for notifications to external systems, if I need to wait until properly running in next kernel. That leaves me the choice of doing notification before executing crash_kexec ? Since I'm apperantly not the only one left with this choice I rather prefer a solution made in public, that is known to be "bad" in some (well known) situations than each and everybody implements their own solution to the same problem. ./Preben _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
