Bug 20106

Summary: ypbind update requires different config format for yp.conf
Product: [Retired] Red Hat Linux Reporter: jon
Component: ypbindAssignee: Alexander Larsson <alexl>
Status: CLOSED WONTFIX QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: http://www.redhat.com/support/errata/RHSA-2000-086-05.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-03-27 17:31:25 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 jon 2000-10-31 16:01:46 UTC 
The security update for ypbind changes the format of /etc/yp.conf in
incompatible ways.

My old yp.conf file, which also works on other Unix platforms, is:

ypserver ds2.gl.umbc.edu
ypserver irix1.gl.umbc.edu
ypserver irix2.gl.umbc.edu
domain slam


This no longer works.

My new file, which does work, is

domain slam server ds2.gl.umbc.edu
domain slam server irix1.gl.umbc.edu
domain slam server irix2.gl.umbc.edu


The only time the config file won't need to be changed is if the user only
uses broadcast mode, as far as I can tell.

The least the announcement should do is warn users of the configuration
change.

At best, it shouldn't change the file. ;-)
Comment 1 jon 2000-11-21 19:31:52 UTC 
This bug is three weeks old; all you guys have to do is release an updated
errata report, not release a new package. Can we have some action on this
please?
Comment 2 Alexander Larsson 2002-03-27 21:54:25 UTC 
It's far to late to change the errata message now, if we release any new errata
for 6.2 i'll mention it though.