Red Hat Bugzilla – Bug 160895
There is no mechanism to remove obsolete booleans from booleans.local
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
Old booleans just stay in booleans.local, and trigger warnings.
The problem is made worse by system-config-securitylevel, because
it doesn't keep track of how booleans.local differs from booleans,
so if you click all over the place, pretty soon the entire
booleans file ends up in booleans.local, regardless of whether
you undid your changes in the same program run, or later.
Also, there should be a button somewhere in the securitylevel tool
to restore all booleans to default state (or perhaps that
should be done per boolean?)
Version-Release number of selected component (if applicable):
*** Bug 169447 has been marked as a duplicate of this bug. ***
I am closing this bug, because old booleans are obsoleted on a
libsemanage-enabled system, and cleared from the config file.