>> One apparently obvious means to do so would be to have a 'kernel
>> log level' for OOPS messages, and let the kernel logging system
>> deal with it. Since this hasn't been done, I would assume there's
>> something wrong with this idea, so perhaps somebody can advise me
>> what?
> Oops are already logged to kernel log.
What as? I have both klogd and syslogd running on my system, and have
had a few oops on various occasions, but have NEVER seen anything in
/var/log/messages relating to them...
> But if klogd or syslogd are not running then the Oops never gets
> written to disk. Alas this occurs all too often.
Even if both are running, it's quite possible the oops won't get
logged as things stand - certainly my impression from examining the
various log files is that they aren't logged, at least with 2.0.3[0-6]
as I've been running on various systems...
One thing I have noticed is that/etc/syslog.conf can be configured to
provide specific log files for specific types of kernel message, and
my thoughts in proposing the above was that if there was a separate
loglevel for OOPS reports, then the various distributors MIGHT be
persuaded to configure their default installations such that all OOPS
reports got logged to a separate logfile - perhaps /var/log/oops or
the like, thus easing the burden somewhat...
> Mind you, the real problem is that users do not read
> Documentation/oops-tracing.txt. I don't think that there is a
> programming solution for that :(.
Perhaps appending a reference to it to the end of every OOPS report
might persuade them to at least see if the file exists on their
system. Many probably don't even know it's there...
Best wishes from Riley.
--- * ftp://ps.cus.umist.ac.uk/pub/rhw/Linux * http://ps.cus.umist.ac.uk/~rhw/kernel.versions.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/