> the only means of escape was the reset button, the oops was written to the
> console but there is no trace of it in the system logs.
>
> This renders a very big problem indeed for 2.2.x systems in remote
> locations, imagen the effect _if_ an scc interface locks up, or any other
> for that matter, there is then no way to restart it.
Well this should be fixed soon. A truly stable kernel should never print
out an OOPS. Hopefully people are working on that right now. Just be
sure nobody has that type of access to your system that you don't trust.
It's also normal behavior for it to print to the console rather than
a log file. If the kernel crashes, it has to assume that the system
as a whole is now unstable so it won't venture *anywhere* (much less to
userland where klogd and your filesystem lives), so it has little choice
but to just print to your console and lock the system up so no further
damage can be done.
David
--
== David Nesting WL7RO Fastolfe [EMAIL PROTECTED] http://fastolfe.net/ ==
