Bug 54765 - pump updates resolv.conf despite -d flag
Summary: pump updates resolv.conf despite -d flag
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pump
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Eido Inoue
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-18 03:17 UTC by A. Campling
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-01-05 16:01:58 UTC
Embargoed:


Attachments (Terms of Use)

Description A. Campling 2001-10-18 03:17:25 UTC
Description of Problem:
Using pump to make a dhcp connection, I noticed that the -d flag seems to
be completely ignored, as is the --no-dns flag, or in pump.conf nodns, also
ignored.  I have a custom /etc/resolv.conf that pump insists on updating,
no matter how much I tell it not to.

Version-Release number of selected component (if applicable):
pump-0.8.11-1 and pump-0.8.11-7

How Reproducible:
every time

Steps to Reproduce:
1. /sbin/pump -d -i eth0

Actual Results:
actually over-wrote custom resolv.conf

Expected Results:
Expected pump NOT to over-write resolv.conf (-d flag)

Additional Information:
$ vi /etc/resolv.conf :

search meat.net
nameserver 64.81.48.19
search figure1.net
nameserver 24.0.43.86

$ /sbin/pump -d -i eth0
$ /sbin/ifconfig:

eth0      Link encap:Ethernet  HWaddr ...  UP BROADCAST RUNNING MULTICAST 
 etc etc etc....
(interface is working, good)

$ vi /etc/resolv.conf :

search telocity.com
nameserver 216.227.80.36
nameserver 216.227.49.36

Uncool.  Does the -d flag really work?  Or am I doing something wrong?  I
even have /etc/pump.conf configured with:

device eth0 {
  nodns
}

And it still overwrites my resolv.conf.  Bleck.
pump-0.8.11-1 and -7 both did this (I updated to see if it fixed the problem).

Comment 1 Eido Inoue 2004-01-05 16:01:58 UTC
closing as supported products don't use pump anymore


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