Bug 475137 - RFE: Don't flood with e-mails if nothing has changed.
Summary: RFE: Don't flood with e-mails if nothing has changed.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-updatesd
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-08 04:31 UTC by Valdis Kletnieks
Modified: 2010-09-02 03:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-08 18:06:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Valdis Kletnieks 2008-12-08 04:31:28 UTC
Description of problem:
So I'm sitting at home, and my not-even-on-the-net laptop squawks that it's just received new e-mail.  Turns out it's yum-updatesd telling me there's a problem updating the system.  True - several RPMs can't upgrade because it includes an update to a shared lib, and several *other* RPMs haven't dropped updated versions into Rawhide yet, and still need the *old* libraries.

But there's no reason to send out 27 e-mails, once per hour.  Nothing has changed since the last time it nagged me.

Recommended change - do a stat() on the involved yum database files and the RPM databases - if none have an mtime less than $run_interval seconds ago, then nothing has changed, so don't bother telling the admin *again*.  Oh, and probably should include /etc/yum/yum-updatesd.conf in the list of files to stat, so it DTRT even on the first iteration.

Version-Release number of selected component (if applicable):
yum-3.2.20-6.fc11.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jeremy Katz 2008-12-08 18:06:12 UTC
The checking (and thus the email) is only done at run_interval.  The default run interval is once an hour though.

Comment 2 Aleksey Nogin 2010-09-02 03:51:03 UTC
IMO it *is* a bug - there is a difference between the "check interval" (1 hour is reasonable) and a "renotification" interval (1 hour is definitely unreasonable for email). Currently yum-updatesd lacks the much needed capability to differentiate between the two. Definitely a valid RFE - which I previously reported as bug 458311 (closed wontfix as well), tried reporting through the RHEL support channel, but somehow can't get anyone to agree it's a valid problem.


Note You need to log in before you can comment on or make changes to this bug.