Red Hat Bugzilla – Bug 178497
up2date-nox --configure does not save some attribute changes correctly
Last modified: 2012-06-20 12:00:04 EDT
+++ This bug was initially created as a clone of Bug #176197 +++
Description of problem:
isatty and networkSetup and possibly other attributes are not saved correctly
when exiting up2date-nox --configure.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run u2pdate-nox --configure
2. Change networkSetup or isatty.
3. <enter> to save
4. Re-run up2date-nox --configure
the new setting was not saved
the new setting was saved
I did not test this for all attributes; there may be others affected.
-- Additional comment from email@example.com on 2006-01-16 11:34 EST --
isatty will get reset everytime the app ones, it's not really a user
networkSetup doesn't get saved intentionally, see bz # 169881
It just shows up in the nox configure stuff because nox configure is lame. I
say, not a blocker, this isn't new behaviour.
-- Additional comment from firstname.lastname@example.org on 2006-01-18 12:57 EST --
I'm taking this one off the blocker list, it's lame but it doesn't really break
anything and is old behaviour
User email@example.com's account has been closed
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.