Running the latest upstream kernel on 17 gets me this.. [ 51.672636] type=1400 audit(1349394421.680:4): avc: denied { write } for pid=597 comm="mrtg" path="/run/systemd/sessions/1.ref" dev="tmpfs" ino=9068 scontext=system_u:system_r:mrtg_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_logind_sessions_t:s0 tclass=fifo_file [ 62.668397] type=1400 audit(1349394432.670:5): avc: denied { write } for pid=836 comm="sendmail" path="/run/systemd/sessions/1.ref" dev="tmpfs" ino=9068 scontext=system_u:system_r:system_mail_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_logind_sessions_t:s0 tclass=fifo_file [ 62.745765] type=1400 audit(1349394432.750:6): avc: denied { write } for pid=837 comm="ping" path="/run/systemd/sessions/1.ref" dev="tmpfs" ino=9068 scontext=system_u:system_r:ping_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_logind_sessions_t:s0 tclass=fifo_file [ 71.905764] type=1400 audit(1349394442.306:7): avc: denied { write } for pid=992 comm="ping" path="/run/systemd/sessions/1.ref" dev="tmpfs" ino=9068 scontext=system_u:system_r:ping_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_logind_sessions_t:s0 tclass=fifo_file [ 81.094477] type=1400 audit(1349394451.496:8): avc: denied { write } for pid=1108 comm="ping" path="/run/systemd/sessions/1.ref" dev="tmpfs" ino=9068 scontext=system_u:system_r:ping_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_logind_sessions_t:s0 tclass=fifo_file [ 90.257829] type=1400 audit(1349394460.656:9): avc: denied { write } for pid=1110 comm="ping" path="/run/systemd/sessions/1.ref" dev="tmpfs" ino=9068 scontext=system_u:system_r:ping_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_logind_sessions_t:s0 tclass=fifo_file [ 110.945396] type=1400 audit(1349394481.346:10): avc: denied { write } for pid=1132 comm="mrtg" path="/run/systemd/sessions/3.ref" dev="tmpfs" ino=13995 scontext=system_u:system_r:mrtg_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_logind_sessions_t:s0 tclass=fifo_file
selinux-policy-targeted-3.10.0-150.fc17.noarch
Do you know what you were doing when this happened?
running mrtg from cron. /etc/cron.d/mrtg : * * * * * root LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l --confcache-file /var/lib/mrtg/mrtg.ok
This looks like it could be a leak?
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.
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.