Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 21090 - RFE: netconfig: setting to disable /etc/resolv.conf rewriting, warnings about bad options
RFE: netconfig: setting to disable /etc/resolv.conf rewriting, warnings about...
Product: Red Hat Public Beta
Classification: Retired
Component: pump (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
David Lawrence
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2000-11-19 12:59 EST by Pekka Savola
Modified: 2007-04-18 12:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-10 19:48:19 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 Pekka Savola 2000-11-19 12:59:23 EST
I personally change the network settings manually with an editor, but I think
netconfig is the only text-mode tool to do this, so...

1) netconfig should have an option that it wouldn't rewrite /etc/resolv.conf.

This is needed on systems that want to use netconfig to configure non-primary interfaces.  
You can avoid this by setting the correct DNS server for every interface, or not using TUI, 
but a real solution might be in order.

2) netconfig should report if invalid options were input.  That is, if you e.g. say:

netconfig -d eth1

Whoops!  The correct syntax was -d=eth1 and netconfig just silently discards the option, 
killing your current eth0 setup (and connection).

In a similar way, something like netconfig --uasdasvaslkdfvla doesn't give a complaint either..
Comment 1 Elliot Lee 2001-09-10 19:48:14 EDT
Part 1) will probably continue to need to be done by editing files - putting a
PEERDNS=no checkbox into netconfig would overcomplicate it.
Comment 2 Elliot Lee 2001-09-10 19:54:39 EDT
Part 2 should be fixed...

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