2008/2/9 Rahul Sundaram <sundaram@xxxxxxxxxxxxxxxxx>: > Valent Turkovic wrote: > > 2008/2/9 Valent Turkovic <valent.turkovic@xxxxxxxxx>: > >> it crashed again: > >> > >> # cat /var/log/setroubleshoot/setroubleshootd.log > >> 2008-02-09 10:36:03,633 [email.WARNING] datoteku nije moguće otvoriti > >> /var/lib/setroubleshoot/email_alert_recipients, No such file or > >> directory > >> 2008-02-09 12:27:44,533 [program.ERROR] Can not handle AVC'S related > >> to dispatcher. exiting > >> setroubleshoot context=system_u:system_r:setroubleshootd_t:s0, AVC > >> scontext=system_u:system_r:setroubleshootd_t:s0 > > > > So when selinux service crashes I have no selinux protection? Isn't > > this a bit of a flaw in design? > > SELinux is not a service. SELinux troubleshooter is and absence of it > does not alter policy. > > Rahul Ok, so my system is still protected but I can't see the issues what happen becuase sel troubleshooter service crashes? To be honesti I prefer it this way :) Valent. -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
