Bug 160895

Summary:	There is no mechanism to remove obsolete booleans from booleans.local
Product:	[Fedora] Fedora	Reporter:	Ivan Gyurdiev <ivg231>
Component:	system-config-securitylevel	Assignee:	Chris Lumens <clumens>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	mclasen
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-01-02 11:42:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	150221

Description Ivan Gyurdiev 2005-06-18 07:08:10 UTC

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 17:35:32 UTC

*** Bug 169447 has been marked as a duplicate of this bug. ***

Comment 2 Ivan Gyurdiev 2006-01-02 11:42:21 UTC

I am closing this bug, because old booleans are obsoleted on a
libsemanage-enabled system, and cleared from the config file.