Cause: $LANG seeting wasn't properly used by cron.
Consequence: Jobs run from crond are not run with the system-wide $LANG setting.
Fix: Cron reads setting of $LANG and use it in jobs.
Result: $LANG setting is used by cron jobs.
+++ This bug was initially created as a clone of Bug #969761 +++
Description of problem:
Jobs run from crond are not run with the system-wide $LANG setting. This results in mail sent by cron being slightly mangled with the wrong content type encoding. This affects any mail that mentions the release name Schrödinger such as mail sent from rkhunter.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. echo $LANG
2. run env from crontab
* * * * * /usr/bin/env
3. wait for the mail from cron
No LANG= reported
LANG= reported and the same as the LANG= setting in /etc/locale.conf
running the env command from a systend started service does confirm that systemd passes that $LANG variable into a service's initial environment. Crond just drops it.
--- Additional comment from Fedora Update System on 2013-06-11 20:56:37 CEST ---
cronie-1.4.10-5.fc19 has been submitted as an update for Fedora 19.
--- Additional comment from Wolfgang Rupprecht on 2013-06-12 01:37:13 CEST ---
Works for me. thanks!
I added karma.
--- Additional comment from Fedora Update System on 2013-06-12 21:11:22 CEST ---
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cronie-1.4.10-5.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
--- Additional comment from Fedora Update System on 2013-06-14 06:52:33 CEST ---
cronie-1.4.10-5.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
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.