* Imre Kaloz <[email protected]> [04.01.2013 16:27]:
>
> I'm fine with the idea but not the way you did it, because if you're "serial
> attached" this gets annoying quite fast. Although we could make this a config
> option and do all kind of magic to set it based on that, I suggest swapping
> your idea: change these through sysctl _after_ a successful boot-up.
>
the problem is: most routers are "in production" and not "serial
attached" - so you have really a problem if a node ("rooftop" or "solar
powered") dies during boot. if you are a developer, you can simple build
your own image and disable this option, all other persons (>90%?) like to
have a running/selfrebooting router when the kernel is panic'ing or there
are serious problems.
with "gets annoying quite fast" i think you mean: during
developing/playing you cannot see the crash-dump, because the unit
is rebooting too fast? then we can simple use the kernel-commandline
argument "panic=30" which leaves 30 seconds before a reboot is
enforced.
also: reading the crashdump after reboot is possible since r32787:
http://intercity-vpn.de/crashlog/
bye, bastian
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
