Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1439217 - cron doesn't treat crontab environment settings right
cron doesn't treat crontab environment settings right
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cronie (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Tomas Mraz
Karel Volný
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-05 08:53 EDT by Karel Volný
Modified: 2018-04-10 07:55 EDT (History)
3 users (show)

See Also:
Fixed In Version: cronie-1.4.11-18.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 07:55:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0738 None None None 2018-04-10 07:55 EDT

  None (edit)
Description Karel Volný 2017-04-05 08:53:02 EDT
Description of problem:
to quote bug 1325088#c8

"Yes, unfortunately cron has a bug that makes it to treat VAR=  lines as erroneous although according to the manual page it should be accepted."

I came across this while trying various MAILTO= values ...

Version-Release number of selected component (if applicable):
cronie-1.4.11-17.el7

How reproducible:
always

Steps to Reproduce:
1. modify /etc/crontab to include 'MAILTO=' line and a job that produces some output
2. wait
3. check root's mail

Actual results:
root gets mail with output of the job

Expected results:
root shouldn't get the output of the job

Additional info:
`man 5 crontab`

An active line in a crontab is either an environment setting or a cron command.  An environment setting is of the form:

          name = value

       where  the  white  spaces around the equal-sign (=) are optional, and any subsequent non-leading white spaces in value is a part of the value assigned to name.  The value string may be placed in quotes (single or double, but matching) to preserve leading or trailing white spaces.

...

If MAILTO is defined but empty (MAILTO=""), no mail is sent.


^ according to the way environment settings should be parsed, the following three should be equal:

MAILTO=""
MAILTO=''
MAILTO=
Comment 12 errata-xmlrpc 2018-04-10 07:55:08 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0738

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