Bug 633509 - With the hash driver DSPAM daily cron job generates output on success.
Summary: With the hash driver DSPAM daily cron job generates output on success.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dspam
Version: 13
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Nathanael Noblet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-13 20:56 UTC by Gustavo Maciel Dias Vieira
Modified: 2010-10-11 19:26 UTC (History)
1 user (show)

Fixed In Version: dspam-3.9.0-9.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-08 12:39:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Patch to fix the issue (403 bytes, patch)
2010-09-13 20:56 UTC, Gustavo Maciel Dias Vieira
no flags Details | Diff

Description Gustavo Maciel Dias Vieira 2010-09-13 20:56:42 UTC
Created attachment 447044 [details]
Patch to fix the issue

Description of problem:

DSPAM runs a daily cron job to clean its databases of unneeded tokens. If DSPAM is configured to use the hash driver, the execution of this cron job will generate output even on successful execution. The line printed is this:

	Hash storage driver detected (not running dspam_clean)

I'm aware that this is not an error, but root will get email about this cron job every day. I believe cron jobs should be silent.


Version-Release number of selected component (if applicable):
dspam-3.9.0-7.fc13.i686
dspam-hash-3.9.0-7.fc13.i686
dspam-libs-3.9.0-7.fc13.i686


How reproducible:
Deterministic

Steps to Reproduce:
1. Configure hash driver
2. Run cron job
3.
  
Actual results:
Output on successful execution

Expected results:
Should run silently

Additional info:

I've attached a patch to fix this problem. The above line should be printed only if "verbose" is set.

Comment 1 Nathanael Noblet 2010-09-16 01:07:24 UTC
Just a FYI - I'm at the second last day of an intensive 3 week course. I'll take a look next week.

Comment 2 Fedora Update System 2010-09-22 16:38:47 UTC
dspam-3.9.0-9.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/dspam-3.9.0-9.fc14

Comment 3 Fedora Update System 2010-09-22 16:38:58 UTC
dspam-3.9.0-9.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/dspam-3.9.0-9.fc13

Comment 4 Fedora Update System 2010-09-22 16:39:10 UTC
dspam-3.9.0-9.fc12 has been submitted as an update for Fedora 12.
https://admin.fedoraproject.org/updates/dspam-3.9.0-9.fc12

Comment 5 Fedora Update System 2010-09-22 16:39:55 UTC
dspam-3.9.0-9.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/dspam-3.9.0-9.el5

Comment 6 Fedora Update System 2010-09-22 18:42:23 UTC
dspam-3.9.0-9.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update dspam'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/dspam-3.9.0-9.fc14

Comment 7 Fedora Update System 2010-10-08 12:39:38 UTC
dspam-3.9.0-9.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2010-10-10 18:01:47 UTC
dspam-3.9.0-9.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2010-10-11 19:23:52 UTC
dspam-3.9.0-9.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2010-10-11 19:26:38 UTC
dspam-3.9.0-9.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


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