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 generated in /usr/lib/mailman/Mailman/ , too) > >I have thought about the way to fix this problem: simply moving the >file to /etc or /var is not enough, because it's part of the package "Mailman" >and lots of files say "from Mailman import mm_cfg" > >any thoughts of this? > thanks and regards, > > Daniel Novotny, Red Hat inc.
I thought RedHat were the experts on this. See <http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html>. 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? If the problem is strictly with mm_cfg.pyc, you may be able to make /usr/lib/mailman/Mailman/mm_cfg.pyc an empty file with mode 0000 (or (0400) so python won't try to write it. If John Dennis is still at RedHat, he may be able to help as I think he's probably thought about this more than anyone. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
