Due to a recent update on Javascript code a full page refresh on your browser might be needed.
Bug 500694 - cronie don't use environment from /etc/crontab
Summary: cronie don't use environment from /etc/crontab
Alias: None
Product: Fedora
Classification: Fedora
Component: anacron
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-05-13 17:54 UTC by Remi Collet
Modified: 2009-06-18 11:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-05-15 12:01:18 UTC
Type: ---

Attachments (Terms of Use)

Description Remi Collet 2009-05-13 17:54:37 UTC

According to man page

"PAM Access Control: On Red Hat systems, crond now supports access control with PAM - see pam(8).  A PAM configuration file for crond is installed in  /etc/pam.d/crond.  crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file."

Standard installation :
/etc/security/pam_env.conf is empty (only comments)
/etc/environment is empty
/etc/crontab :


But for running task :


So I think value should be taken from /etc/crontab.
What did I miss ?

Comment 1 Tomas Mraz 2009-05-13 19:52:01 UTC
I suppose that you're editing either user's crontab with crontab -e or some crontab in /etc/cron.d/ directory. Each crontab is individual and the environment variables specified in that crontab apply only to that crontab.

Comment 2 Remi Collet 2009-05-14 04:58:47 UTC
No, it's a /etc/cron.hourly script (provided by ocsinventory-agent rpm, which need /sbin in path).

Where is defined the defaut environment for it ?

- Previously, hourly task where launch by "run-parts" in /etc/crontab, so use the env. defined there

- It seems it is now launched by /etc/cron.d/0hourly where there is no env. defined

This seems to explain the difference between F10/F11 which can be consider as a "regresion".

I don't have done any test for daily/monthly script, but it could be a solution to add same env. in /etc/cron.d/0hourly that in /etc/crontab to keep same behaviour than in previous release.


Comment 3 Tomas Mraz 2009-05-14 06:46:16 UTC
Yes, that's a good idea.

Comment 4 Marcela Mašláňová 2009-05-15 12:01:18 UTC
The cron man page will be updated and cron jobs in anacron package has environment values now.

Comment 5 Fedora Update System 2009-06-09 14:34:55 UTC
anacron-2.3-75.fc11 has been submitted as an update for Fedora 11.

Comment 6 Fedora Update System 2009-06-18 11:50:28 UTC
anacron-2.3-75.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

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