Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Robin, could you please attach AVC msgs?
0.o Where the hell did my edits go?? You know I'd never do that to you! Anyways. AVCs: type=AVC msg=audit(04/02/2013 09:12:59.101:5501) : avc: denied { write } for pid=5254 comm=touch name=error dev="vda2" ino=4321 scontext=system_u:system_r:initrc_t:s0 tcontext=system_u:object_r:mailman_log_t:s0 tclass=file ---- type=AVC msg=audit(04/02/2013 09:12:59.103:5502) : avc: denied { write } for pid=5254 comm=touch name=error dev="vda2" ino=4321 scontext=system_u:system_r:initrc_t:s0 tcontext=system_u:object_r:mailman_log_t:s0 tclass=file Piping that through audit2allow -R got me a tweak that does the right thing. The problem is with this line: ExecStartPre=/bin/touch /var/log/mailman/error in /etc/systemd/system/multi-user.target.wants/mailman.service I have no idea how it was working before. As always, my systems have unconfined off. -Robin
*** Bug 947522 has been marked as a duplicate of this bug. ***
In case you still want it: rlpowell@stodi> ps -eZ |grep initrc system_u:system_r:initrc_t:s0 736 ? 00:00:00 shellinaboxd system_u:system_r:initrc_t:s0 749 ? 00:00:00 shellinaboxd system_u:system_r:initrc_t:s0 11643 pts/20 00:00:00 ssh -Robin
Yes, you got it. It is caused by ExecStartPre=/bin/touch /var/log/mailman/error
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
selinux-policy-3.10.0-171.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-171.fc17
Package selinux-policy-3.10.0-171.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-171.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-13082/selinux-policy-3.10.0-171.fc17 then log in and leave karma (feedback).
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.