public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] app-admin/mcelog daily cronjob?
Date: Thu, 17 Apr 2014 22:26:35 +0200	[thread overview]
Message-ID: <20140417222635.29c5fda7@gentoo.org> (raw)
In-Reply-To: <9F184909-C037-4439-B94E-D2F7D395EAFE@stellar.eclipse.co.uk>

On Thu, 17 Apr 2014 18:13:57 +0100
Stroller <stroller@stellar.eclipse.co.uk> wrote:

> 
> On Thu, 17 April 2014, at 2:32 pm, Tom Wijsman <TomWij@gentoo.org>
> wrote:
> >> ...
> >> Do you seriously consider it up for debate whether or not it's a
> >> bug, when daily error messages are produced and emailed to the
> >> system admin?
> > 
> > That depends on whether you consider that to be the expected
> > behavior for the way it has been set up; the cause is already
> > known, wrong perms.
> 
> Well, it seems to be the Gentoo devs that set it up this way.
>
> You're the expert - you tell me why this is happening.

Your found information and the post installation messages tell this:

  "Traditionally mcelog was run as a cronjob, but this usage is
  deprecated now. The modern way to run it is to start it at
  boot up time and run it always as a daemon."

  "A sample cronjob is installed into /etc/cron.daily
  without executable bit (system service is the preferred method now)"

There is nothing extra for a non-maintainer to add to this.

> You haven't given me any explanation why this package is on a
> freshly-installed Gentoo system, you haven't told me in the Gentoo
> install docs that I need to configure this package, have you?

That is because you have installed it; and if you did install it, then
the useful post installation messages tell you this information.

To demonstrate that this is the case, app-admin/mcelog is ...

... not part of the current stage3 as revealed by its contents list;

    $ grep app-admin/mcelog stage3-amd64-20140410.tar.bz2.CONTENTS
    $

... not pulled in by another dependency as recorded in the database;

    $ grep --include='*DEPEND' -rl app-admin/mcelog /var/db/pkg/
    $

... not pulled in through profiles and therefore not by the @system set

    $ grep -r app-admin/mcelog /usr/portage/profiles/
    $

... and not listed as the dependency of any package in the Portage tree.

    $ grep --include='*.ebuild' --exclude='mcelog-*' -r app-admin/mcelog /usr/portage/
    $

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D


  reply	other threads:[~2014-04-17 20:27 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
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 [this message]
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=20140417222635.29c5fda7@gentoo.org \
    --to=tomwij@gentoo.org \
    --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