RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1439217 - cron doesn't treat crontab environment settings right
Summary: cron doesn't treat crontab environment settings right
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cronie
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Karel Volný
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-05 12:53 UTC by Karel Volný
Modified: 2023-09-07 18:51 UTC (History)
3 users (show)

Fixed In Version: cronie-1.4.11-18.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 11:55:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0738 0 None None None 2018-04-10 11:55:20 UTC

Description Karel Volný 2017-04-05 12:53:02 UTC
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 11:55:08 UTC
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.