Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 160895 - There is no mechanism to remove obsolete booleans from booleans.local
There is no mechanism to remove obsolete booleans from booleans.local
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
: 169447 (view as bug list)
Depends On:
Blocks: FC5Target
  Show dependency treegraph
Reported: 2005-06-18 03:08 EDT by Ivan Gyurdiev
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-02 06:42:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ivan Gyurdiev 2005-06-18 03:08:10 EDT
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):

How reproducible:
Didn't try

Additional info:
Comment 1 Chris Lumens 2005-09-29 13:35:32 EDT
*** Bug 169447 has been marked as a duplicate of this bug. ***
Comment 2 Ivan Gyurdiev 2006-01-02 06:42:21 EST
I am closing this bug, because old booleans are obsoleted on a
libsemanage-enabled system, and cleared from the config file.

Note You need to log in before you can comment on or make changes to this bug.