On 01/04/2009 02:40 PM, Daniel J Walsh wrote:
setroubleshoot will die if it finds an AVC about it self to prevent
an
infinite loop of avcs.
setroubleshoot can send itself a signull on both Rawhide and F10 with
the latest updates.
What caused it to have a problem ? Is this expected behaviour for
setroubleshootd - or is something amiss that caused it to get the signull ?
Do I need to write a monitor script to keep restarting it ?