Bug 74506

Summary:	yp.conf reverts to "broadcast" during network (re)initialization
Product:	[Retired] Red Hat Linux	Reporter:	Ben Levenson <benl>
Component:	ypbind	Assignee:	Steve Dickson <steved>
Status:	CLOSED WONTFIX	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	trondeg
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-05-10 16:45:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ben Levenson 2002-09-25 16:09:05 UTC

Description of Problem:
network (re)initialization causes ypbind to revert server setting to 
broadcast.

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

How Reproducible:
100%

Steps to Reproduce:
1. configure ypbind to point to a specific server (verify contents of yp.conf)
2. restart network services
3. notice "broadcast" setting in yp.conf

Additional Information:
FWIW -- 
/etc/sysconfig/network:
 NETWORKING=yes
 HOSTNAME=localhost.localdomain
 NISDOMAIN=redhat.com

/etc/sysconfig/network-scripts/ifcfg-eth0:
 DEVICE=eth0
 BOOTPROTO=dhcp
 ONBOOT=yes

Comment 1 Alexander Larsson 2002-10-02 07:10:33 UTC

I don't get that. Can you try without DHCP?

Comment 2 Trond Eivind Glomsrød 2003-04-15 10:51:28 UTC

This still happens with Red Hat Linux 9, and is extremely annoying in an
environment with lots of temporary YP servers... especially since they can't be
configured to only listen to the private network they're created to serve

Comment 3 Ben Levenson 2006-05-10 16:45:29 UTC

(bugzilla housekeeping)
closing due to inactivity.