Hi Julien,
I discussed the timestamp idea with Andi Kleen, and, basically, it's
of no use because the precision of the timestamp would suck.
The kernel collects MCE data every 5 minutes by default, then mcelog
runs every 5 minutes, collecting the data collected by the kernel.
[..]
Andi
Michael Renner [EMAIL PROTECTED] wrote:
Hi,
Uhm, if I've got a logfile full of MCE entries after (e.g.) returning
from a weeks vacation a timestamp with a granularity of 5 minutes is
That'd be 10 minutes, not 5, and it can be even more than that under
some circumstances.
better than none,
Michael Renner [EMAIL PROTECTED] wrote:
Hi,
That'd be 10 minutes, not 5, and it can be even more than that under
some circumstances.
If I run the collector every 5 minutes fetching all messages that have
been generated since the last invocation the granularity should be 5
minutes, or am I
Julien BLACHE wrote:
Michael Renner [EMAIL PROTECTED] wrote:
Uhm, if I've got a logfile full of MCE entries after (e.g.) returning
from a weeks vacation a timestamp with a granularity of 5 minutes is
That'd be 10 minutes, not 5, and it can be even more than that under
some circumstances.
Package: mcelog
Version: 0.7-1
Severity: wishlist
It would be nice if mcelog could log timestamps in its logfile. A quick
hack for doing that would be:
foo=`/usr/sbin/mcelog --ignorenodev --filter`; if [[ $foo ]]; then echo
-e `date`\n$foo /var/log/mcelog; fi
best regards,
Michael
--
Michael Renner [EMAIL PROTECTED] wrote:
Hi,
It would be nice if mcelog could log timestamps in its logfile. A quick
hack for doing that would be:
foo=`/usr/sbin/mcelog --ignorenodev --filter`; if [[ $foo ]]; then echo
-e `date`\n$foo /var/log/mcelog; fi
It'd be nice, but I'd like to have
6 matches
Mail list logo
