[Yum-devel] [PATCH 04/10] Minor changes to default yum-cron settings.

Matthew Miller mattdm at mattdm.org
Fri Jul 29 16:42:40 UTC 2011


On Fri, Jul 29, 2011 at 12:12:15PM -0400, James Antill wrote:
>  I pushed everything but this patch.

Cool, thanks.

> > This sets MAILTO to root by default, instead of empty. The script still
>  This seems fine, to me.

Do you want a separate small patch for just this change?

> > Second, DEBUG_LEVEL is set to 1, so that a useful, basic amount of
> > information is included in the updates.
>  This I'm less sure about ... I know a lot of people complain about
> output from yum-cron ... do you have examples of before/after of what
> the above change does?

It's the difference between silence and:

================================================================================
 Package         Arch          Version                     Repository      Size
================================================================================
Updating:
 binutils        x86_64        2.21.51.0.6-6.fc15          updates        3.3 M

Transaction Summary
================================================================================
Upgrade       1 Package(s)

Total download size: 3.3 M


>  Anyone else have an opinion?

I actually don't think the current options make much sense. The yum commands
aren't consistent -- check-update gives output if there are packages
available even with debuglevel set to 0, while update, which actually _does_
something, is silent. And the mail is generated if there's any output.

What I'd like to do is have the script better know if the action was
successful and what the results were (i.e. were updates available and/or
applied?) and have it configurable at a high level whether you want e-mail
reports on errors only, errors and warnings, on all changes, or on all runs,
and how verbose you want each report to be.

In the meantime, I'm fine with the default being 0.


-- 
Matthew Miller           mattdm at mattdm.org          <http://mattdm.org/>


More information about the Yum-devel mailing list