From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id EBF49138A1F for ; Thu, 17 Apr 2014 20:27:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E8D02E0BD1; Thu, 17 Apr 2014 20:27:36 +0000 (UTC) Received: from albert.telenet-ops.be (albert.telenet-ops.be [195.130.137.90]) by pigeon.gentoo.org (Postfix) with ESMTP id 9B16BE0AA7 for ; Thu, 17 Apr 2014 20:27:35 +0000 (UTC) Received: from localhost ([94.226.55.127]) by albert.telenet-ops.be with bizsmtp id r8Ta1n00a2khLEN068Ta43; Thu, 17 Apr 2014 22:27:34 +0200 Date: Thu, 17 Apr 2014 22:26:35 +0200 From: Tom Wijsman To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] app-admin/mcelog daily cronjob? Message-ID: <20140417222635.29c5fda7@gentoo.org> In-Reply-To: <9F184909-C037-4439-B94E-D2F7D395EAFE@stellar.eclipse.co.uk> References: <931458D2-51AE-47CF-97B2-8DD1EFBBE56A@stellar.eclipse.co.uk> <20140416164407.0e2b1ab8@gentoo.org> <20140416175217.48c391b9@gentoo.org> <6BA9E690-963A-4E0D-9448-7D0DA7D45F3D@stellar.eclipse.co.uk> <20140416184134.3887226e@gentoo.org> <20140417153236.773b471e@gentoo.org> <9F184909-C037-4439-B94E-D2F7D395EAFE@stellar.eclipse.co.uk> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 47c53abb-e953-4452-aeaf-ecb0a1f355e3 X-Archives-Hash: 5e02391bcc52ebad54808e1efcb72039 On Thu, 17 Apr 2014 18:13:57 +0100 Stroller wrote: > > On Thu, 17 April 2014, at 2:32 pm, Tom Wijsman > 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