Bug 113386 - [PATCH] ypbind init script doesn't support DHCP assigned NIS servers
Summary: [PATCH] ypbind init script doesn't support DHCP assigned NIS servers
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: ypbind
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karel Klíč
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-13 14:20 UTC by Joshua Weage
Modified: 2013-03-03 22:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-10 13:59:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Fix to ypbind init script to read DHCP provided NIS servers (2.87 KB, text/plain)
2004-01-13 14:22 UTC, Joshua Weage
no flags Details

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.


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