public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] app-admin/mcelog daily cronjob?
Date: Wed, 16 Apr 2014 18:30:22 +0200	[thread overview]
Message-ID: <534EB01E.30404@gmail.com> (raw)
In-Reply-To: <6BA9E690-963A-4E0D-9448-7D0DA7D45F3D@stellar.eclipse.co.uk>

On 16/04/2014 18:14, Stroller wrote:
> 
> On Wed, 16 April 2014, at 4:52 pm, Tom Wijsman <TomWij@gentoo.org> wrote:
>>
>> There is no such indication in that reply. That is up to you to decide.
> 
> Well, I posted here looking for useful answers and perhaps a full explanation (like, of how this is needed beyond the system logger), not vapid one-liners. 
> 
> I guess I'll just file a vapid-one bug that my Gentoo system is generating these cron messages, rather than first trying to come to a understanding of the cause. Would that make the developers' lives easier? 
> 
> Stroller.
> 
> 
> 
> 


mce is Machine Check Exception; it's a hardware trickery that watches
for and records faults in hardware.

Consider something like Dell's fancy monitoring softwares, the results
don't magically appear in syslog - you use Dell's client app to query
the hardware, figure out what the bits means then you can look-see what
is going on. mcelog is sort of in the same class of software, but it's a
generic interface.

You don't *have* to use it, the machines will run just fine without it.
You will lack some monitoring though that could be useful - that's your
call.

As for the cron job files, by all means file a bug. At a minimum you'll
get an answer as to what the dev thinks about that deprecation status.

-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2014-04-16 16:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 13:39 [gentoo-user] app-admin/mcelog daily cronjob? Stroller
2014-04-16 14:44 ` Tom Wijsman
2014-04-16 15:39   ` Stroller
2014-04-16 15:52     ` Tom Wijsman
2014-04-16 16:14       ` Stroller
2014-04-16 16:30         ` Alan McKinnon [this message]
2014-04-16 16:41         ` Tom Wijsman
2014-04-17 12:11           ` Stroller
2014-04-17 13:32             ` Tom Wijsman
2014-04-17 17:13               ` Stroller
2014-04-17 20:26                 ` Tom Wijsman
2014-04-17  3:58 ` Randy Barlow
2014-04-17  8:49 ` Neil Bothwick
2014-04-17 12:15   ` Stroller
2014-04-17 12:28     ` Neil Bothwick
2014-04-17 17:17       ` Stroller
2014-04-17 19:47         ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=534EB01E.30404@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox