Re: [Mailman-Users] mm_cfg.py in /usr : SELinux problem

2009-04-04 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Apr 3, 2009, at 2:21 PM, Mark Sapiro wrote: Since the RedHat package already installs its own /etc/init.d/mailman, I think this is a good solution for the RedHat package. For the rest of us, we're pretty far from FHS compliance and presumably goo

Re: [Mailman-Users] mm_cfg.py in /usr : SELinux problem

2009-04-03 Thread Mark Sapiro
Daniel Novotny wrote: > >The solution I created is to create a new script called >"mailman-update-cfg"'which contains the following: > >#!/usr/bin/python >import py_compile > >py_compile.compile("/usr/lib/mailman/Mailman/mm_cfg.py") > >in the mm_cfg.py there's a note, that if you use SELinux, >you

Re: [Mailman-Users] mm_cfg.py in /usr : SELinux problem

2009-04-02 Thread Daniel Novotny
- "Mark Sapiro" wrote: > I understand your issue with mm_cfg. All I can suggest is symlinks > might help. I thought the current RedHat package currently has a > symlink /etc/mm_cfg.py -> /usr/lib/mailman/Mailman/mm_cfg.py (or vice > versa). Does this help? yes, the symlink is there, but neve

Re: [Mailman-Users] mm_cfg.py in /usr : SELinux problem

2009-04-01 Thread Mark Sapiro
Daniel Novotny wrote: > >we are now having a problem, how to adapt mailman configuration (mm_cfg.py) >to SELinux policy: > >it resides in /usr and the SELinux maintainer argues /usr should be read-only, >which is not satisfied, when you change the configuration (and the .pyc file >has to be generat

[Mailman-Users] mm_cfg.py in /usr : SELinux problem

2009-04-01 Thread Daniel Novotny
hello, we are now having a problem, how to adapt mailman configuration (mm_cfg.py) to SELinux policy: it resides in /usr and the SELinux maintainer argues /usr should be read-only, which is not satisfied, when you change the configuration (and the .pyc file has to be generated in /usr/lib/mailman