Description of problem: I noticed that the initscript for setroubleshoot has a 'cleardb' entry that refers to /var/lib/setroubleshoot/database.xml: cleardb(){ running=0 [ -e /var/lock/subsys/$prog ] && running=1 [ $running == 1 ] && stop echo $"Clearing database" rm -f /var/lib/setroubleshoot/database.xml [ $running == 1 ] && start return 0 } But I don't seem to have that file: [tbl@localhost init.d]$ ls -l /var/lib/setroubleshoot total 256 -rw------- 1 root root 251139 2007-10-11 09:42 audit_listener_database.xml [tbl@localhost init.d]$ /usr/lib/python2.5/site-packages/setroubleshoot/config.py refers to audit_listener: 'database' : { 'database_dir' : { 'value' : '/var/lib/setroubleshoot', 'description' : '', }, 'filename' : { 'value' : 'audit_listener', 'description' : '', Is there a mismatch here? Version-Release number of selected component (if applicable): setroubleshoot-1.10.7-1.fc8 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Does this patch 'fix' this? --- setroubleshoot 2007-10-02 18:15:29.000000000 -0700 +++ setroubleshoot.new 2007-11-18 16:40:23.000000000 -0800 @@ -109,7 +109,7 @@ [ -e /var/lock/subsys/$prog ] && running=1 [ $running == 1 ] && stop echo $"Clearing database" - rm -f /var/lib/setroubleshoot/database.xml + rm -f /var/lib/setroubleshoot/*database.xml [ $running == 1 ] && start return 0 }
Appears fixed in setroubleshoot-2.0.0-3.fc9 Close?
*** Bug 433385 has been marked as a duplicate of this bug. ***