Am 31.01.2013 22:04, schrieb Ranjan Maitra:
Jan 31 15:01:35 localhost systemd[1]: Failed to start
firewalld - dynamic firewall daemon.
Jan 31 15:01:35 localhost systemd
[1]: Unit firewalld.service entered failed state
Jan 31 15:01:36 localhost setroubleshoot: SELinux is
preventing /usr/bin/python2.7 from getattr access on the
file /run/firewalld.pid. For complete SELinux messages. run sealert -l
6da93ecc-b84a-4d14-bc3f-0f8d06af82a2 Jan 31 15:01:37 localhost
setroubleshoot: SELinux is preventing /usr/bin/python2.7 from write
access on the file firewalld.pid. For complete SELinux messages. run
sealert -l d6eea039-e995-4e5e-a6f3-57048fc05bae
Jan 31 15:01:37 localhost
setroubleshoot: SELinux is preventing /usr/bin/python2.7 from unlink
access on the file firewalld.pid. For complete SELinux messages. run
sealert -l 689b4650-7ccb-4ca7-a2db-2ec6c5f18b6f
Not sure what to do with all this
write a bugreport why this new shiny thing is broken by
SElinux and realize that such things are the reason why
i said "reboot blidnly" is a terrible idea
AND START IPATBLES AGAIN BEVAUSE YOU ARE WIDE OPEN NOW