Bug #13487
closedcrontab entry creating multiple emails
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1303161
Description of problem:
The crontab that is created for scap reporting generates an email even when nothing is wrong. This causes a larger issue on big environments. I'd like to see the STDOUT be redirected to /dev/null, and only STDERR generating an email.
Version-Release number of selected component (if applicable):
All
How reproducible:
This is standard behavior. This is a feature change more than a bug report
Steps to Reproduce:
1. install from RPM
2. Schedule a scan
3. verify crontab on remote system
Actual results:
An email is sent containing the STDOUT form the crontab to the root user
Expected results:
The system should only email when there is an issue with the crontab, not during normal processing.
Additional info:
https://github.com/theforeman/puppet-foreman_scap_client/pull/13 covers this change, however it was never implemented. You can modify the /usr/share/puppet/modules/foreman_scap_client/manifests/init.pp file by hand, however any new RPM upgrade will override that change.
Updated by Shlomi Zadok about 8 years ago
- Status changed from New to Closed
- Pull request https://github.com/theforeman/puppet-foreman_scap_client/pull/13 added