Bug 113386

Summary: [PATCH] ypbind init script doesn't support DHCP assigned NIS servers
Product: Red Hat Enterprise Linux 3 Reporter: Joshua Weage <weage98>
Component: ypbindAssignee: Karel Klíč <kklic>
Status: CLOSED WONTFIX QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: rvokal
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: 2010-05-10 13:59:23 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:
Attachments:
Description Flags
Fix to ypbind init script to read DHCP provided NIS servers none

Description Joshua Weage 2004-01-13 14:20:32 UTC 
Description of problem:
The ypbind init script doesn't bind to NIS servers provided by DHCP.

Version-Release number of selected component (if applicable):
1.12-1

How reproducible:
Always

Steps to Reproduce:
1.  Enable DHCP
2.  Setup DHCP server to provide NIS server
3.  Clients don't bind to NIS servers
  
Actual results:
NIS not working

Expected results:
ypbind to bind to NIS server.

Additional info:
Comment 1 Joshua Weage 2004-01-13 14:22:07 UTC 
Created attachment 96942 [details]
Fix to ypbind init script to read DHCP provided NIS servers

This init script will use NIS servers provided by DHCP.  It requres an
additional variable to be set in /etc/sysconfig/network: DHCPNIS=yes
Comment 2 Steve Dickson 2007-04-17 19:59:31 UTC 
I did think it was a good idea to have the init script look 
in /etc/yp.conf for the domain name but I didn't think that
action should be governed by DHCP.

Please try ypbind-1.19-9
Comment 3 Karel Klíč 2010-05-10 13:59:23 UTC 
The fix will not get into RHEL-3.