Bug 76688 - redhat tool should reflect current situation
redhat tool should reflect current situation
Status: CLOSED DUPLICATE of bug 25510
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-10-24 18:13 EDT by matteo porta
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-24 18:13:11 EDT
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 matteo porta 2002-10-24 18:13:05 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Virgilio6pc)

Description of problem:
i've used the redhat gui tool to change the security level (firewall)
i've changet the level, saved it, closed the app and then re-launched it. when 
the window opened i was still seeing the old setting.
i assume that the utility works, ie it has really changed the settings...
then i think that on startup the tool should read the current config and show 
it accordingly. it's fundamental: since i don't know (and i don't want to know) 
the details of setting security level, i can't decide if the tool effectively 
worked or not...
this request is valid for other config tools, like lokkit, as an example.
ps under windows the tools works like i'm suggesting...
if you want to ease the transition from windows you should really update all 
your tools.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. load the gui tool for changing the security level
2. change the security level, save and quit.
3. reload the tool
4. it is still showed the old setting

Additional info:
Comment 1 Bill Nottingham 2002-10-24 18:53:08 EDT

*** This bug has been marked as a duplicate of 25510 ***

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