Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 220

Summary: Some cron jobs generate "No message, no subject; hope that's ok"
Product: [Retired] Red Hat Linux Reporter: Marc MERLIN <marc_soft>
Component: crontabsAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-04-10 22:02:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marc MERLIN 1998-11-29 01:00:37 UTC 
This is an old bug forwarded to your new bug tracking system

Logrotate will sometimes send empty mails when it rotates
logfile on a time basis (when one of the files rotated is
empty, and logrotate is configured to mail the logfile that
is going to be erased)

There are other cron jobs that can generate empty mails
sometimes (I haven't bothered to track them down, but I know
they exist).

I think it'd be a good idea to modify /etc/crontab as
such:
#
run-parts
02 * * * * root run-parts /etc/cron.hourly | grep -v "Null
message body; hope that's
ok"
07 1 * * * root run-parts /etc/cron.daily | grep -v "Null
message body; hope that's
ok"
12 2 * * 0 root run-parts /etc/cron.weekly | grep -v "Null
message body; hope that's
ok"
17 3 1 * * root run-parts /etc/cron.monthly | grep -v "Null
message body; hope that's ok
Comment 1 Cristian Gafton 1998-12-10 23:46:59 UTC 
Altough sometimes thos emessages can be annoying, som people count on
mail from cron to see if a job completed. We can not arbitrarily
filter cron mails by default, that falls under the responsabiliries of
the system administrator.