Bug 50740 - neat does not clean up the /etc/wvdial.conf file when a Modem entry is deleted
neat does not clean up the /etc/wvdial.conf file when a Modem entry is deleted
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
7.3
i386 Linux
low Severity low
: ---
: ---
Assigned To: Ngo Than
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-02 15:05 EDT by Panic
Modified: 2008-05-01 11:38 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-02 17:45:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Panic 2001-08-02 15:05:08 EDT
Description of Problem:

When a modem entry is deleted, the /etc/wvdial.conf file is not cleaned up
-- the old entries remain and build up.  The entry obviously can be
removed, because creating another entry with the same name replaces the old
entry; however, it only does so when neat is closed, and not before.

How Reproducible:

Always

Steps to Reproduce:
1. create an entry in neat for a modem.
2. note the entry in /etc/wvdial.conf that corresponds to that entry
3. delete the entry in neat
4. note that /etc/wvdial.conf has not been updated, and the old entry is
still in place.

Actual Results:

/etc/wvdial.conf is not updated to reflect the removal of the entry in neat.

Expected Results:

/etc/wvdial.conf should be cleaned up.

Additional Information:
Comment 1 Glen Foster 2001-08-02 17:44:56 EDT
This defect is considered SHOULD-FIX for Fairfax.
Comment 2 Ngo Than 2001-08-05 11:56:12 EDT
It's fixed in CVS

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