Bug 129920 - Please don't call "/usr/bin/python" from /etc/cron.d/mailman
Summary: Please don't call "/usr/bin/python" from /etc/cron.d/mailman
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mailman
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: John Dennis
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3Target 457388
TreeView+ depends on / blocked
 
Reported: 2004-08-14 08:51 UTC by Russell Coker
Modified: 2008-07-31 11:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-31 20:17:03 UTC


Attachments (Terms of Use)

Description Russell Coker 2004-08-14 08:51:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)

Description of problem:
In SE Linux the program that is executed determines the domain that the program is run in.

Running "/usr/bin/python -S /var/mailman/cron/nightly_gzip" from /etc/cron.d/mailman causes the cron job to run in domain sysadm_crond_t, while running it as "/var/mailman/cron/nightly_gzip" (with the first line of the script being "#!/usr/bin/python -S") causes it to run in domain mailman_queue_t which is the desired result (*).

This change will not have any affect for people who don't use SE Linux and will do a lot of good for SE Linux users.

(*)  Please note that there are other problems with SE Linux and mailman, this change is not all that's required to make it work - but it is the only change that's required in the mailman package.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
examine /etc/cron.d/mailman

Additional info:

Comment 1 John Dennis 2004-08-31 20:17:03 UTC
Thank you for your help and support of mailman in Red Hat. I have
modified the rpm as per your suggestions and the results appear in
mailman-2.1.5-12 which is currently building for rawhide and inclusion
in FC3 and RHEL4.


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