On Thu, 17 Apr 2014 18:17:35 +0100, Stroller wrote:

> > That assumes that everybody has mcelog installed, they don't.  
> 
> Since I don't recall installing it, I assume that this is now being
> shipped as part of world.

It's no t on anything here. @world is empty, I take it you mean @system.
That is defined by the current profile so if it had been added, anyone
running the latest profile would have it - I am and I do not.

If it's in @world, you put it there.

> >> I'm pretty sure a cron USE flag is in use elsewhere, I think it would
> >> be better to have an option to install the package without the cron
> >> script, rather than having to delete it manually each time one
> >> upgrades the package.  
> > 
> > That's a fair point, except you don't have to delete anything. If the
> > execute permission is not set, the script does not run.  
> 
> I think it's reasonable not to expect a daily error message from
> default settings which the user hasn't been advised to configure. 
> 
> I don't know whether the script is being run or not, but assuming this
> package is causing this error message (which is the assumption under
> which you made this reply), the error is being produced. 

I'm only following on from your assumption. I see no reason why a
disabled cron script should cause an error message, but it's your system
and you know enough for me to follow your judgement. If you are still
uncertain what is causing the messages, surely finding out must be your
priority.


-- 
Neil Bothwick

Don't take life too seriously, you won't get out alive.

Attachment: signature.asc
Description: PGP signature

Reply via email to