On Mon, 2010-02-22 at 10:45 +0800, Zhu, Peter J wrote:
Kerneloops scanner should scan syslog at startup once
and then dmesg regularly. Original implementation
Inverted relative to what?
Please see patch. Any comments?
I did the same somethime ago, and then was told by kerneloops people
that it was actually intended that dmesg is scanned first
and syslog after it, repeatedly.
The scanning is inherently hard to get right.
What if scan happens when only part of the oops is in the log?
what if machine hung mid-oops and was rebooted,
leaving half-oops in the middle of the log?
If you have a scenario where you observe an incorrect behavior,
please describe it.